C++ pitfalls hard to avoid that are elegantly managed in Rust

[trentj]

Here's something I wrote on the subject in another thread:

in an interactive program, ignoring failures (which cin >> does by default ) is always the wrong thing. [...] cin >> is optimized to make the worst behavior (turning decoding errors into junk data) the easiest thing to do. And it has this extra thing where it does arbitrary and inconsistent things with leading or trailing characters. In fact, I think it’s impossible to use cin responsibly for interactive programs because its behavior with respect to whitespace is just too weird; you should always use readline instead.

[...]

it’s actually just as easy or slightly easier to do all this stuff correctly in Rust. It’s only the wrong stuff, the things you should almost never do, that’s easier in C++.