> Almost none of that ecosystem is relevant to kernel.
What exactly leads you to believe that?
From the Rust 2021 survey, 2420 said they use nightly to access one or more language features they need, 1028 claimed a Crate dependency requires it, and 876 claimed a tool they use requires it.
This, from a sample pool where around 3k users out of around 10k claim they use a nightly version.
Again. Almost none of these can run in kernel space, those that are required will be duplicated in tree.
The survey results are not relevant. The rust code must not use stdlib (the name escapes me) which uses an incompatible memory allocation mechanism.
The code used to build will likely need to be checked into the kernel git repo and not downloaded live online, I doubt that the mature development process of the kernel wants the problems that other package managers have.
I will fight to ensure that this is not the case in the kernels that I work with, because fetching dependencies is for people who can tolerate other people and networks being faulty.
Because the kernel code isn’t pulling dependency code from the internet OR a compiler that changes every day. Kernel code will be checked into the repo, dependencies if any, will be vendored. Nor will much of crates.io be relevant - the kernel will only use no_std with fallible allocations.
As for the compiler, it will use a pinned, stable compiler, not nightly.
Why are you spreading FUD about nightly + Linux on this thread? At no point has this combination ever been considered.
What exactly leads you to believe that?
From the Rust 2021 survey, 2420 said they use nightly to access one or more language features they need, 1028 claimed a Crate dependency requires it, and 876 claimed a tool they use requires it.
This, from a sample pool where around 3k users out of around 10k claim they use a nightly version.