Does anyone know if zigs reached the point of maturity to having solved most compiler bugs? I used it a couple years ago and it failed HORRIBLY for anything real I was throwing at it.
I’ve been using zig for hobby projects for the last few months and have yet to run into a compiler bug. Tracking down comptime errors can be a little bit confusing, but I’ve found the compiler to be stable and useable.
The switch to the Zig implementation fixed a ton of bugs, but introduced way more new ones. I've used it in anger for almost a year and simply gave up at some point and switched to Rust because of the buggy build-ins and broken compiler error messages.
Tbh I doubt that this situation will improve now that they bit off even more from the compiler cake after having more than they can chew already.
Isn't the idea that bootstrapping the compiler let's people who only know zig contribute to the compiler? Might it be too premature to declare failure?
In theory maybe, but after watching Andrew Kelleys latest talks I don't get the feeling that the Zig implementation is build for readability and correctness, but an experiment for exploring the design space of data-driven-design in compilers.
We switched to a self-hosted implementation of the compiler since then. The old compiler had various age-related issues, Cpp-related issues and it made little sense to fix it since the plan was to replace it anyway.
The new compiler is a much better codebase and compiler bugs get fixed much more quickly and effectively.
Maturity to fix most compiler bugs? Yes, on x86_64 (some bugs remain on other architectures). But you can still expect your code to break between zig versions.