4 ms·

Zig keeps overflow checks in the main release mode (ReleaseSafe), Rust defines ints as naturally wrapping in release. This means that Rust is not a strict super

Zig keeps overflow checks in the main release mode (ReleaseSafe), Rust defines ints as naturally wrapping in release. This means that Rust is not a strict superset of Zig in terms of safety, if you want to go down that route. I personally am not interested at all in abstract discussions about sets of errors. Reality is much more complicated, each error needs to be evaluated with regards to the probability of causing it and the associated cost. Both things vary wildly depending on the project at hand.

avgcorrection 4y ago
> This means that Rust is not a strict superset of Zig in terms of safety, if you want to go down that route. Fair. > I personally am not interested at all in abstract discussions about sets of errors. Abstract? Handwaving “no silver bullet” is even more abstract (non-specific).
Avshalom 4y ago
releasesafe is the main release mode because zig has a small community that is largely ideologically aligned with it. I have absolutely no faith that, in a future where Zig is popular, it will remain so. "well it passed our unit tests and it didn't fall down when we fuzzed it, so lets squeeze a couple free % extra perf out of it and ship" already in this post we have people talking about how safer mallocs or sanitizers are too much of a hit to expect people to use in the wild.