As much as I love Rust, I think it has to stabilize a few things first, like its async/await story. A part of the community is very unhappy with it and IMO not addressing this would lead to a premature adoption of Rust in the Linux kernel which will end up creating legacy code that’s almost as ugly and hard to maintain as the olden C code is.
An absolutely valiant effort but I do wonder if it’s not coming too soon.
Yeah I quite agree that async was rushed a bit… It’s still a very nice coroutine system to use though, it doesn’t need to be purely for async use. ^.^
Beside, kernel work will not use async anyway.
Ah, then if that’s the case then IMO Rust is quite ready to do hardcore heavy lifting.
Async is ‘technically’ zero-cost, but most executors want to be very generic, and so to do so they need to allocate a tiny little bit of memory for each task, and the kernel doesn’t like allocating when possible, so it wouldn’t use it. It could technically still use, say, the async keywords for known typed continuation related functionality, but honestly I don’t really see that.