Wooster

stage1/zig.h has a lot of changes. All I did was `zig build update-zig1 --zig-lib-dir lib`. So, most changes are coming from the second commit, but I guess it's intended?

That could very well be it. Maybe it's ok to do it here. I might split it into 3 commits at least, though. Also, I can see a CI failure,...

Not yet sure what's up here. Running `zig build test --zig-lib-dir lib` gives me an enormous amount of memory leak logs bigger than my terminal buffer size. I seem to...

So I ran the `zig build test-std` tests locally and they all passed so I suspect this is an issue outside the std and possibly caused by the stage1/zig.h changes...

Another PR of mine #14782 is hit with the exact same CI failure. Can anyone tell me the correct way to rebuild `stage1/`? I don't seem to be doing it...

So this has some interesting build-related breaking changes: ```zig const std = @import("std"); pub fn build(b: *std.Build) void { const optimize = b.standardOptimizeOption(.{}); const target: std.zig.CrossTarget = .{ .os_tag =...

Why?

Does this fix #7600 or #5148? See also #12400 where I think there's already been a lot of discussion.

Great!

Another API I just thought of would be `exit(.success)`, `exit(.failure)`, and `exit(.{ .other = 5 })`. This however will break everything but it'd be an option as well. Advantage is...