News for hackers. Stuff that matters.
Re:What makes Nim practical? by def- on Friday January 23, 2015 @10:40AM (#8935342)
> - Significant whitespace, but tabs are forbidden

Here's the reasoning: https://github.com/Araq/Nim/wiki/Whitespace-FAQ#tabs-vs-spac...

If you still want tabs you can add this at the top of your files and they work:

    #! replace("\t", "  ")
> - Identifiers are case and underscore-insensitive (FOO_BAR === fooBar === fo_ob_ar)

This changed recently, now the first letter is considered case sensitive: http://nim-lang.org/manual.html#identifier-equality

Re:What makes Nim practical? by CyberShadow on Friday January 23, 2015 @11:03AM (#8935488)
> Here's the reasoning: https://github.com/Araq/Nim/wiki/Whitespace-FAQ#tabs-vs-spac....

Honestly, there are less drastic solutions to these problems. Some languages (forgot which) simply forbid mixing tabs and spaces when the tab size makes the code ambiguous. And their C example will generate an "ambiguous else" warning in D, which you can disambiguate by adding braces.