Hacker News Reader

I am no expert on Rust, but I think targeted optimized algorithms are what the unsafe trait is for. That way you can profile and choose when programming and debugging.

Rust actually gives you access to all overflow behaviors that you could want. So if you know that your target CPU has saturating overflow you use https://doc.rust-lang.org/std/primitive.i32.html#method.satu... or wrapping_add, or overflowing_add, or checked_add. The syntax isn't as nice as for normal + though.

Is there a way to specify that I don't care? That's exactly what C undefined behavior is for.

I'd take predictable slow software on some platforms over unpredictable fast software any day.

In rust, integer overflows are defined to be wrapping, which is how it works automatically on essentially every architecture Rust supports.