4 ms·
Modern C++ isn’t spatially or temporally memory safe, which are the primary benefits in question. You can write subsets of C++ that are spatially safe (and you
by woodruffw 5y ago
Modern C++ isn’t spatially or temporally memory safe, which are the primary benefits in question. You can write subsets of C++ that are spatially safe (and you have been able to for quite some time), but temporal safety is completely out the window. And note: those limited spatial guarantees also go out the window as soon as you interact with third party code.
- kramerger 5y agoKernel code is by design "insecure". You can bend over backwards to make it look secure (see the few Rust OS implementations that exist today), but at the end of the day you can't combine "safe" languaues and real memory security as you are modifying page tables and programming DMA using raw addresses.
- woodruffw 5y agoBoth the OpenSSF and Linux Foundation work on things other than the kernel. (But even beyond that: Rust has an entire sublanguage ("unsafe Rust") that's intended for these purposes. The point of unsafe Rust is to do things that are safe but the compiler can't reason about, so that subsequent safe Rust can rely on abstractions built in unsafe code.)