4 ms·
Quoting from the link, this is what gets me: Nim is case- and underscore-insensitive (except for the first character). Thus HelloWorld and helloWorld are diffe
by pacman128 6y ago
Quoting from the link, this is what gets me:
Nim is case- and underscore-insensitive (except for the first character).
Thus HelloWorld and helloWorld are different, but helloWorld, helloworld, and hello_world are all the same
I really don't understand this feature of the language.
- rntksi 6y agoIt's because it integrates with C libraries where a lot of variable naming schemes could be found, and tries to let you do your thing regardless of included C libs. Took me some time to understand to but once I tried it, it's pretty cool.
- bE9a3S5So8igd3 6y agoExcept that Nim doesn't allow double-underscores, which show up from time to time in C. Compiling var my__thing = 10 yields: Error: invalid token: trailing underscore Which is actually my biggest complaint about Nim. The error messaging is terrible, as are some of the decisions around the standard library. There's a good amount of bad and Windows-centric language there, unfortunately. Functions in the standard library like "setCtrlCHook" https://nim-lang.org/docs/system.html#setControlCHook%2Cproc%29 https://nim-lang.org/docs/system.html#setControlCHook%2Cproc... Overall still a fan of Nim. Unlike many of the people in this thread, "marketing" is not a concern to me. I don't expect to ever program with Nim at my day job because "marketing" programmers are too dogmatic these days. Day-job languages are always going to be hypelang_2020 + dogma_patterns_v3. I very much like that the Nim community feels underground, is small and active. I hope it never suffers from the influence of modern dayjob programmers, but this is because I've seen the fun sapped out of other communities. A selfish desire, if I may.