Re:Rust for C++ programmers – part 3: primitive types and op...
by nrc on Wednesday April 23, 2014 @02:10AM
(#7632426)
All array indexing is bounds checked, so those kind of errors are prevented. We're still working on the story around overflow checking
[ Parent
| on HN ]
Re:Rust for C++ programmers – part 3: primitive types and op...
by sisalcat on Wednesday April 23, 2014 @02:16AM
(#7632444)
This prevents buffer overflow errors, but not crashes.
Re:Rust for C++ programmers – part 3: primitive types and op...
by dbaupp on Wednesday April 23, 2014 @02:24AM
(#7632475)
It prevents the OS killing a misbehaving application (which is what is meant by "crash" in that context). This allows, for example, a multithreaded server application to continue even if one worker task indexes an array incorrectly.
Re:Rust for C++ programmers – part 3: primitive types and op...
by kzrdude on Wednesday April 23, 2014 @05:11AM
(#7632942)
It also prevents an equally important problem: silent passing of errors. It's common for out of bounds accesses or stores in C or C++ to just pass silently, potentially corrupting data.