2 ms·
They said it, but it's a platitude - a lie. If this results in a broken kernel because the Rust part was not updated, the C change will be reverted to get a wor
by immibis 2y ago
They said it, but it's a platitude - a lie. If this results in a broken kernel because the Rust part was not updated, the C change will be reverted to get a working kernel. This makes C maintainers de facto responsible for learning Rust to update the bindings.
- steveklabnik 2y agoThat is simply not true. That is why Rust is an experiment currently: it is allowed to break. Compiling the Rust code at all requires an extra flag to be passed, so breaking Rust code never breaks normal builds.
- immibis 2y agoThis is already the treatment given to out of tree kernel modules. Why not do the experiment out of tree?
- steveklabnik 2y agoRust has already demonstrated its usefulness out of tree, with stuff like binder in Android and the GPU driver for the M1 with Asahi Linux. With those successes, upstream is interested in seeing what Rust in-tree would look like. Hence the in-tree experimentation going on now.
- Pet_Ant 2y agoThey don't need to learn Rust. They could reach out and get help from someone that does. I'm sure the Rusteceans would be happy to if it got more support for C.