News for hackers. Stuff that matters.

A comment on Zig – Type Resolution Redesign and Language Changes. Parent comment

Re:Zig – Type Resolution Redesign and Language Changes by thezipcreator on Thursday March 12, 2026 @01:25AM (#47346841)
I'm not sure why you shouldn't make your compiler accept CRs (weird design decision), but fixing it on the user-side isn't exactly hard either. I don't know an editor that doesn't have an option for using LF vs CRLF.

The unused variable warning is legitimately really annoying though and has me inserting `_ = x;` all over the place and then forgetting to delete it, which is imo way worse than just... having it be a warning.

[ Parent | on HN ]
Re:Zig – Type Resolution Redesign and Language Changes by CyberDildonics on Thursday March 12, 2026 @10:45AM (#47351314)
I don't know an editor that doesn't have an option for using LF vs CRLF.

And I don't know any other languages that don't parse a carriage return.

The point is that it was intentionally done to antagonize windows even though they put out a windows version. Some people defend this by saying that it's easy to turn off, some people defend it by saying windows users should be antagonized.

No zig people ever said this was a mistake, it was all intentional.

I'm never going to put up with behavior like that with the people making tools actively working against me.

[ Parent | on HN ]
Re:Zig – Type Resolution Redesign and Language Changes by thezipcreator on Thursday March 12, 2026 @03:11PM (#47355662)
> And I don't know any other languages that don't parse a carriage return.

fair enough.

[ Parent | on HN ]