News for hackers. Stuff that matters.
Re:Zig – Type Resolution Redesign and Language Changes by dnautics on Wednesday March 11, 2026 @11:18AM (#47336760)
negative. For example bounds checking is turned on by default in Zig, which prevents classes of overflow safety errors.
Re:Zig – Type Resolution Redesign and Language Changes by simonask on Thursday March 12, 2026 @03:47AM (#47347696)
I don't think you've necessarily understood the scope and impact of the borrow checker. Bounds checking is just a sane default (hygiene), not a game changer.
Re:Zig – Type Resolution Redesign and Language Changes by dnautics on Thursday March 12, 2026 @04:42PM (#47356785)
I mean, I'm the author of this?

https://github.com/ityonemo/clr

so yes, I understand that it's important. It doesn't need to be in the compiler though? I think it's likely the case that you also don't need to have annotations littering the language.

Re:Zig – Type Resolution Redesign and Language Changes by simonask on Friday March 13, 2026 @08:20AM (#47363451)
I wish you good luck! Successive attempts to achieve similar levels of analysis without annotations have failed in the C++ space, but I look forward to reading your results.
Re:Zig – Type Resolution Redesign and Language Changes by dnautics on Friday March 13, 2026 @02:57PM (#47368205)
yeah afaik you cant easily intercept c++ at a meaningful IR in the same way as you can zig. Zig's AIR is almost perfect for this kind of thing.