3 ms·
still relevant today, but as someone who writes a lot of Zig code I haven't ever really encountered it in the wild. You definitely could, though, and it'd be wi
by slimsag 3y ago
still relevant today, but as someone who writes a lot of Zig code I haven't ever really encountered it in the wild. You definitely could, though, and it'd be wildly confusing.
Luckily, the Zig core team has recognized it is an issue and plan to address it before 1.0 :)
- Cloudef 3y agoIt's rare to hit it, but if you do, having it happen silently is not ideal for sure.
- ForkMeOnTinder 3y agoI still think noalias-by-default is the way to fix this. https://github.com/ziglang/zig/issues/1108 https://github.com/ziglang/zig/issues/1108 You get all the benefits of Zig being able to choose the function ABI, but if the optimization would have caused a bug, you'll get an immediate panic at the function entrypoint, instead of silently corrupted data.