> The downside is that the "revisit the failure modes" step never happens. You exaggerate, but yes crap code exists. As I said, however, you can spot it from

> The downside is that the "revisit the failure modes" step never happens. You exaggerate, but yes crap code exists. As I said, however, you can spot it from across the room with grep -r 'unwrap()'. That's all I ask; can work be evaluated easily? Rust doesn't guarantee correctness; thus unsafe{} pragmatically exists. Rust just makes much incorrectness more obvious and easier to detect, both for the coder and for those upon whom their work is foisted.