Meghan Denny
Meghan Denny
I can add it back, but do you have a use case where it would be needed to make that disambiguation? there weren't any places where that was being done...
does this reproduce if you git clone and build from source? you mention above this is using fedora sentry
while this could be helpful, i think the error should stay as is. an argument could be made that the suggestion could potentially be useful as a note, but its...
https://ziglang.org/documentation/master/#atomicLoad https://ziglang.org/documentation/master/#atomicStore
not sure when exactly it regressed but I looked into this recently and the initial suggestion of marking `std.fmt.format` as `inline` and seeing how that affects codegen and compilation time...
that's tracked in https://github.com/ziglang/zig/issues/14931
Using `.NoReturn` for this case doesn't make sense because it represents an expression that causes a runtime exit of the target artifact. whereas `.CompileError` would mean an expression that halts...
well for that case in the meantime they would have to add `.?` but long term im hopeful for https://github.com/ziglang/zig/issues/9260 which would change that to `fn foo(a: infer A, b:...
@zigazeljko is that not the same `a.out` kinda file that gets output by default of `zig cc` when you dont specify `-o` ?
wasnt it established previously that something as big and use case-dependent as this should be prototyped in 3rd party packages first, especially now that the package manager exists?