3 ms·
I don't see how this is required for one drop and if that's the use case, it sho_uLd only be used there and not everywhere. It makes it harder for tooling and f
by karmakaze 8y ago
I don't see how this is required for one drop and if that's the use case, it sho_uLd only be used there and not everywhere. It makes it harder for tooling and for searching for all references. Inconvenient, like spaces in filenames.
- nimmer 8y agoOne of the main benefits is in wrapper libraries for C. Another one is using libraries that have a naming style that I don't like. Searching for names is not a problem as people don't mix different styles within the same project. Also there's nimgrep for this. Finally, getting a compiler error when I try to use variables called should_run and shouldrun in the same scope is a feature, not a bug: it encourage using less misleading names.
- karmakaze 8y agoIf it treated 'same scope' to mean something more like a module (i.e. library), that would be better. Also, it should never consider hell_owl and hello_w_l to be the same, although each could match hellOwl and helloWL. Basically it takes the style-insensitivity too far.
- nimmer 8y agoAnd yet, after using Nim for many years hell_owl == hello_w_l has never been a problem. Again, it warned me in few occasions when I tried using confusing names like new_dir and newdir. There are style guides and nimpretty to help further.