Re:Committing to Rust for Kernel Code
by insanitybit on Thursday November 23, 2023 @02:51PM
(#38396777)
> and the "escape hatch" of "unsafe {}" ended up being 1000x more error prone that C.
IMO this is the biggest issue right now. `unsafe` needs some refinement, certainly.
> the overall trend was more in trying to defend Rust with whatever it takes.
This can sometimes be the case, unfortunately. But fwiw I think a lot of us in the community agree entirely that there's room to improve in the unsafe world.
IMO this is the biggest issue right now. `unsafe` needs some refinement, certainly.
> the overall trend was more in trying to defend Rust with whatever it takes.
This can sometimes be the case, unfortunately. But fwiw I think a lot of us in the community agree entirely that there's room to improve in the unsafe world.