If zig was being developed using a process where correctness mattered one jot, then the underlying issue wouldn't have kept happening and you wouldn't have kept papering over a fundamentally wrong model. While I did not compare zig to V, now that you brought it up in a related comment, you're right, they do seem to follow very similar development models: "That's not an issue, and even if it is an issue, we've already fixed it, and even if we haven't fixed it, it doesn't matter, and even if it matters, it's not our job, and even if it is, you can't prove it." Wow.
Zig is a toy language with a broken implementation. The comptime story is incoherent; it is two entirely unalike languages being written with superficially similar (but not identical) syntax, and lots of bugs in the gaps. At least V is honest about what it is and isn't.
ETA: I provided links, do you have any evidence whatsoever that any of these issues have been fixed? Because I went through these links and 0% of them have commits attached. 0% of them have comments from a developer indicating they've been fixed (other than comments posted after I shared links). 0% of them have comments from a developer saying that they're being held open in order for testcases to be added. Your claims are just more confabulation from a confirmed liar.