Silver
Silver
Your clang build script for windows doesn't provide any optimization options. If you provide -O2 or -Ofast, I expect you will see the same result as zig cc
Option 2 seems like the most Zig-ish to me, and existing usage can be fixed by `zig fmt`. I think it's worth noting that there's no precedent for option 3:...
> it seems fine to me for fn (comptime T: type) T and fn (comptime T: type) id(T) to be considered distinct Consider this case: ```zig const std = @import("std");...
Zig currently types `execve` with an error set return type (ie. `error { ... }`, as opposed to an error union `error { ... }!T`). I do agree that `!noreturn`...
Not really sure how Andrew's comment there is relevant here. Canonicalizing helps with searchability, as @castholm says, and if you really want to disable it you can turn off zig...
canonicalizing helps with searchability in the common case because it means you can search for `@"\t"` and find all the fields that are named a single tab character. Your usecase...
I like this idea in concept but I think it needs more discussion and should be a proposal.
Why are you using `zig cc` if you want to use a separate c compiler? `zig cc` does not call a separate c compiler, it *is* a c compiler.
One small request: it would be really nice if this returned `u32` or another smaller integer type, instead of `usize`
Could you provide a code sample that reproduces this issue?