Why not devote the time to writing a better memory safety tool for the Linux kernel (or C in general) rather than keep trying to force two disparate cultures and ideologies to meet in some fantasy middle?
ThePrimeagen actually had an interesting opinion on this recently too, worth a watch: https://www.youtube.com/watch?v=62oTu9hjxL4
It’s also not just about memory safety. Greg in particular has recognized how Rust’s type system will be helpful for preventing other kinds of bugs, for example.
But not in the Linux kernel. Any new effort will be greenfield, why rally around an entirely different programming language instead of writing a novel tool?
> Greg in particular has recognized how Rust’s type system will be helpful for preventing other kinds of bugs
Do you have any examples here?
Sure, it is still an experiment, but that's irrelevant: your theoretical "make C memory safe" tooling does not exist and does not exist in the kernel.
> instead of writing a novel tool?
Do you have a proposed design for the novel tool? Many have tried, nobody has succeeded.
> Do you have any examples here?
From the article:
> Kroah-Hartman said that it could eliminate entire classes of bugs in the kernel.
He's said similar things elsewhere: https://social.kernel.org/notice/AlxbVeMxyJNsLoNa6q
Kernel devs should just put on their big boy pants and go with the times. C is simply not the right tool for the job anymore for a lot/most kernel work.
I think the Rust developers weren't even asking for that. They just want the C developers to sign up to some semantics. But the C developers know the function interface has evolved to be merely functional: it works, but with few invariants, riddled with caveats and few cross-function guarantees. It can't be hoisted into meaningful semantics, no less a type system, particularly across 10 filesystem API's.
Rust developers should focus on drivers in subsystems with stable API's, instead of trying to stabilize what decades of work has failed to.