Re:Next steps for Rust in the kernel
by pohl on Wednesday September 21, 2022 @11:02AM
(#32926152)
There might be some merit to that, although it could just be the case that they just don't like the idea of a compiler telling them what they can and cannot do.
[ Parent
| on HN ]
Re:Next steps for Rust in the kernel
by mustache_kimono on Wednesday September 21, 2022 @01:42PM
(#32928571)
"Hey man, don't harsh my buzz. I want give out two mutable aliases to this underlying value. I know what I'm doing."
Narrator: He didn't know what he was doing.
Re:Next steps for Rust in the kernel
by nyanpasu64 on Wednesday September 21, 2022 @02:12PM
(#32928962)
Giving out two mutable aliases to an integer or struct holding integers is perfectly safe in C and C++ and JS and Java and Python... and perfectly safe in Rust if you hand out multiple &struct and mark each field as Cell<T> (just with painful syntax compared to any other imperative language in existence).