It all started a couple months ago when I found a // TODO delete hard tabs from the language in the code. I of course immediately filed a PR to remove it (I say that jokingly, the comment was placed in the stack unwinding code, which needs to handle tabs as they are allowed in other language like C/C++ which may be in the callstack. This is what the PR actually addresses), but it’s been stuck in the pile of PRs waiting for review so I never heard back on it.
Of course a TODO comment in the code is not a commitment to anything.
Now just a few minutes ago, I saw a new comment from andrew:
- hard tabs become errors again, but fixed by zig fmt
I’m using tabs in my codebase, and there are many reason to do so, some objective, many subjective. Surely I’m not the only one, and this was a big drama pre-0.10.0. I don’t want history to repeat itself here.
I can get behind many decisions that involve having a uniform style and making code more readable, but in my opinion this goes to far. It’s not even providing any visible or function change to the code.
And it’s a futile attempt anyways. If this lands, I for my part will do what I have done in 0.9.0: Remove tabs in a build step before passing source files to the compiler
Am I the only one here who uses (or wants to use) tabs in Zig? How many language users are we going to lose over a new tabs vs spaces war? Is this really worth it?