> "unsafe" is in practice often needed for performance in Rust That's the power of Rust, not a limitation of it. Rust thrives on its ability to provide safe in

> "unsafe" is in practice often needed for performance in Rust That's the power of Rust, not a limitation of it. Rust thrives on its ability to provide safe interfaces over unsafe code. You'll see this practice in other languages too; if you're coding safe Java, you're using a lot of unsafe code from the JVM and via JNI. If you're using Python, the stdlib and all the performance-sensitive libraries (numpy, pandas, etc) are written in unsafe code, but even when you import those we still say your Python code is safe, and that Python overall is a memory safe language.