@sfiedler wrote in ziglang/zig#35336 (comment):
Try zig build test --fuzz -Doptimize=ReleaseSafe
How did you test it?
CallModifier in langref with what's actually there
CallModifier in langref with what's actually there
std.PriorityQueue an unmanaged container
ensureTotalCapacityPrecise is pub on ArrayList why shouldn't it here?
I was reading std and found this, probably applicable? https://ziglang.org/documentation/master/std/#std.Io.random
Converting to lowercase should be unnecessary, according to the MDN docs it's case sensitive. Therefore you can just change the entries in the Month enum to be capitalized and then do stringToEnum....
Just some things I thought about when reading through the PR.
I think most people write ".{ .nanoseconds = nanoseconds };"
spelling
spelling
The naming convention for zig regarding constants is just snake_case. https://ziglang.org/documentation/master/#Names
Why use a slow crypto.random here. not that this is a performance sensitive place. Idk how other places in the codebase handle things like this.
the first one should be status.class() == .server_error
The ": Io.Timestamp" is unnecessary on lhs or?
I feel like this should just be replaced with a std.meta.stringToEnum this seems redundant.