3 ms·
Because then when you want to write a module in Rust, all your interfacing with the rest of the kernel will be done through C function calls, with C semantics,
by kelnos 2y ago
Because then when you want to write a module in Rust, all your interfacing with the rest of the kernel will be done through C function calls, with C semantics, and C expectations of ownership. There's really little point to adding Rust abstractions to the kernel, then, at least when it comes to modules.
- cozzyd 2y agoBut without a stable ABI can you expect modules to realistically work across versions? It seems like a similar problem to shared libraries, which rust punts on.
- deleted 2y ago[deleted]
- tasn 2y agoThe kernel doesn't offer a stabke ABI for modules regardless of Rust. So what you're describing is already the case.
- cozzyd 2y agoSure, it changes when something changes, but with rust it changes (in theory) without any code changes but with a tool chain change.
- steveklabnik 2y agoThe point is that there’s no requirement at all, so the rate of change is irrelevant.