Allow Windows line endings

[haferburg]

Treat '\r' as whitespace in the zig and the C tokenizer.

[haferburg]

Cf. #581 #576 #574

[andrewrk]

We will allow \r\n in C but not in zig

[haferburg]

@andrewrk Oh, ok. Sorry to hear that. On #574 you wrote

One thing we can do is allow crlf but replace them with zig fmt (when it exists)
that's why I implemented it.

May I ask why? The implementation is very simple. It's not going to make the grammar more complicated. I can absolutely understand that you won't allow '\r' in the git repo. But in user code?

[thejoshwolfe]

There's a lengthy discussion on Zig's policy on line ending style and indentation style here: #544

Someone (probably me) should write a summary and put it in the docs. Until then, that thread is the best explanation.

[haferburg]

The way I see it, you have two choices:
∙ Provide plugins or configuration advice in a 'getting started' section for all major editors that deal with the line ending issue.
∙ Accept '\r'.

And frankly, if I had known that zig doesn't allow tabs for indentation, I would not have considered it. And I don't even use tabs. But this is a philosophy that has nothing to do with zen. It comes across as "we're right and everyone else should just accept that they're wrong", even on such a non-issue. All this is going to achieve is drive away people for no good reason. Especially considering how easy this is to implement.

[thejoshwolfe]

Provide plugins or configuration advice in a 'getting started' section for all major editors that deal with the line ending issue.

• Notepad: not supported.
• All other text editors: use Unix (LF) line endings.

That's really all there is to it.

This philosophy does have to do with the zen of zig: only one obvious way to do things. It's not about who's right and wrong; it's about making everyone do it the same way.

[paul-reilly]

It takes serious introspection to back out of a previously strongly held position so please consider that Windows users are - or will probably form - a majority of new users to Zig as it goes mainstream and that CRLF is the default line ending of this supported platform. Importantly, it's not just text editors that need reconfigured - I've never had any issues with git pulling as CRLF in the past, for example. Is the standing advice to memorize git commands to clone zig repos with different settings or make a global change to suit one language? I think reducing these points of friction would be the pragmatic choice and would increase the robustness, optimality and maintainability of the decision to use Zig on Windows. :)