Strange you should mention this because they’ve been working on and will continue to work features to make Rust more suitable to the Linux kernel. This issue (https://github.com/Rust-for-Linux/linux/issues/355) for features in rustc was opened a year ago and it seems half done.
> backwards and forwards compatibility
Backwards compatibility has existed for 7 years, since Rust 1.0. If your code ever compiled under any version of Rust since 1.0, it will compile with all future versions. Guaranteed.
Forwards compatibility - not sure how this would be guaranteed. If your code uses a new library API, how would an old tool chain compile that? AFAIK, this is a non goal.
> calm down
I think it calmed down after async stabilised 4 years ago. I don’t recall seeing big changes since then.
On a broader note, Rust’s 6-week release cycle might make it seem like big features are being added all the time, but I don’t think this is the case. It’s usually just a few small features or conveniences, some bug fixes, minor improvements to compile times.
The fact that it’s hard to even remember that these things have happened is a testament to how rarely it happens and how well the breakage is handled.
I suspect folks see the Rust release notes on the HN front page and assume that it must be a blockbuster release with lots of move-fast-break-things to make it there. But it’s actually like “new library API, some const fns, compilation time improvements”.
So then they think “this language is moving waaay too quickly, they need to do LTS versions”. But this is just speculation. That’s why I asked GP. Maybe they’ve actually experienced breakage.
I expect these to become even less frequent with ever rising amounts of Rust code that isn't on Github.
At least in regards to the features that affect kernel-level development. Stabilizing that doesn't preclude active development in things like async or in the standard library (both of which I'd expect not to see much or any use in the kernel.) But I'd hope for decent work towards backwards and forwards compatibility in the set of language features used there.