&gt; In Jai it is easy to, for example, have bounds checks on during the entire development process to aid in finding bugs, then turn off bounds checks in a dozen critical loops for testing and release, then turn bounds checking on in one loop that still proved crash-y.<p>That&#x27;s pretty much exactly Rust&#x27;s philosophy as well.<p>&gt; Rather than Rust&#x27;s &quot;Safe All The Things!&quot; approach, bounds checking is just another tool you can use or not use as is appropriate for the context.<p>Rust&#x27;s philosophy is not &quot;Safe All The Things&quot;. It has &quot;unsafe&quot; for a reason.<p>Anyway, I really dislike the overfocus on bounds checks, because they&#x27;re pretty much zero overhead if properly implemented and optimized.