> This leads to a strategy of only having checks in "safe" mode. Where the "fast" mode is just as "unsafe" as C. This is hard to describe without getting deep

> This leads to a strategy of only having checks in "safe" mode. Where the "fast" mode is just as "unsafe" as C. This is hard to describe without getting deep into Rust details, but I think the ability to encapsulate unsafe code in safe APIs is just as important as what pure safe code can do. (Of course those two things end up being intimately related.)