4 ms·
Maybe it's just because I'm getting older, but I struggle to read Nim when I'm forced to use two spaces for indentation. I can barely make out each block of cod
by Daunk 2y ago
Maybe it's just because I'm getting older, but I struggle to read Nim when I'm forced to use two spaces for indentation. I can barely make out each block of code, and I don't like to rely on my IDE to make a language readable.
- jasfi 2y agoI was also a bit taken aback by the 2 space indentation. But after a bit of practice I got used to it.
- Daunk 2y agoMaybe, it's just so hard to read for me. Also, my IDE isn't all fancy, so tab is tab, I'd have to space it all myself...
- netbioserror 2y agoI use it at work for an important CLI tool that backs a number of our systems. My style is almost exactly like Python. Four-space tabs, snake_case, my own rules for indenting parameters and keywords. You do not need to use the official Nim style, you can absolutely write it like Python, Ada, however you like.
- Daunk 2y agoThe compiler seems to enforce spaces? But I did see some code that replaces tabs with spaces, but it feels dirty having that in every single source file.
- netbioserror 2y agoMaybe I was unclear, I guess I should say my indents are 4 spaces. Never tried it with actual tabs so I can't say.
- deleted 2y ago[deleted]