4 ms·
I personally think it's a great idea. Much better than having a code base with mixed camelCase and snake_case because a library didn't follow the language conve
by BoppreH 8y ago
I personally think it's a great idea. Much better than having a code base with mixed camelCase and snake_case because a library didn't follow the language convention.
I've seen people write wrappers just to fix casing.
- joelthelion 8y agoA much better solution is to have a language-wide style guide, with a tool such as "go fmt" to enforce it.
- alehander42 8y agoInterop with C/JS: you can't control all identifiers, because you can reuse a rich ecosystem of other language libs: you can't force their names to change EDIT: you can still change them in importc pragmas, but this still seems less nice to me. Still, you can reuse Nim libs even if they don't follow nep1: one can still use nimpretty/gofmt for his own codebase.