It is relatively easy to create a situation where you overflow your program. See here: https://github.com/rust-lang/rust/issues/50049
Googling around, there are many situations where bad code can lead to an overflow and your code breaking.
> Rust is another step into the beyond. When finishing a feature and its test suite I’ll run my program to see it in action, but just as a formality – I already know it works. I also know that it’s going to keep working because meticulousness of the compiler is so good at catching regressions.
> I already know it works
This is the part I don't agree all of the time, but depending on the scope and size of the project, I've seeing this be true. And the compiler is really good at catching regressions, submitting PRs for Rust projects is not easy in the beginning, but it is very hard to insert a regression.
Trying to explain otherwise to them is an exercise in futility. Because ownership/borrowing.
So serious Rust project members may never claim this, but there is a large less widely experienced Rust community who have turned the claims Rust does make into something much stronger and more resistant to logic.
fn main() {
let a = 3;
assert(a == 2, "a should definitely be 2");
}
let buf = [0u8; 810241024];