3 ms·
At the limit, `unsafe` blocks would still be necessary for any FFI used to call into C code, which is trivially proven unsafe. It's mistaken to think of `unsaf
by kibwen 12y ago
At the limit, `unsafe` blocks would still be necessary for any FFI used to call into C code, which is trivially proven unsafe.
It's mistaken to think of `unsafe` as a novel language feature. All other languages merely defer their unsafe shenanigans to native C calls. I can just as easily write a memory-unsafe program in Python. In Rust, we use `unsafe` to hoist logic out of C wherever possible, to make our code even more safe; even the unsafe dialect of Rust is safer than C.