If Rust is pointless because sometimes you need unsafe blocks, then memory protection is also pointless because sometimes you have to switch to ring 0.
-
-
Creating hard privilege layers, whether via the kernel/userspace separation or via compile-time safety boundaries, improves security/safety. We have conclusive evidence of this from the fact that AFL finds far fewer memory safety problems in Rust code than C/C++.
-
Yes but at what level should the layer be designed? IMO the existence of unsafe is never a problem, it's really that to build a sophisticated fast program, sometimes unsafe is the only solution in places where you won't expect it. That's the problem with Rust's unsafe now.
- 1 more reply
New conversation -
-
-
It is missing some point but the argument stands: if something as simple as memset still requires unsafe, I tend to think something fundamental in the design of unsafe is flawed
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.