News for hackers. Stuff that matters.
Re:Linus Torvalds: Rust for the Kernel Could Possibly Be Mer... by cmrdporcupine on Thursday June 23, 2022 @10:16AM (#31849449)
As other commenters have poked at; I'd hope that if Rust is going into the kernel (even if just for drivers), that means it's hopefully hopefully started to "calm down" as a language.

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.

Re:Linus Torvalds: Rust for the Kernel Could Possibly Be Mer... by nindalf on Thursday June 23, 2022 @03:26PM (#31854048)
> At least in regards to the features that affect kernel-level development.

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.

Re:Linus Torvalds: Rust for the Kernel Could Possibly Be Mer... by mllllv on Thursday June 23, 2022 @10:38AM (#31849726)
It hasn’t. Rust is 12 years old, has no specification, incomplete documentation, a borrow checker that won’t allow some valid code today but may allow that same code tomorrow, and a level of complexity that is seriously next level. It’s about as calm as C++ on cocaine in my opinion.
Re:Linus Torvalds: Rust for the Kernel Could Possibly Be Mer... by phendrenad2 on Thursday June 23, 2022 @01:56PM (#31852803)
I expect that Rust will kind of fork, like Python 2.x vs 3.x (remember that?). We'll have "stable Linux rust" and "move-fast-and-break-things meme Rust". Those of us who value stability will say "Thank you Linus Torvalds" and just use the "Linux rust" for everything.
Re:Linus Torvalds: Rust for the Kernel Could Possibly Be Mer... by nindalf on Thursday June 23, 2022 @06:27PM (#31855866)
Could you give an example of a Rust release breaking existing compiling code? The Rust Project goes to great lengths to avoid this. For example, before every release they try to compile every open source Rust codebase with the release candidate compiler.
Re:Linus Torvalds: Rust for the Kernel Could Possibly Be Mer... by steveklabnik on Thursday June 23, 2022 @07:52PM (#31856484)
There have been a few. It often comes down to something that was previously unsound being made an error. There’s been long deprecation periods when this happens.

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.

Re:Linus Torvalds: Rust for the Kernel Could Possibly Be Mer... by nindalf on Friday June 24, 2022 @02:11AM (#31858307)
Hey Steve, thanks for the response. I was struggling to remember, which is why I asked.

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.

Re:Linus Torvalds: Rust for the Kernel Could Possibly Be Mer... by phaylon on Friday June 24, 2022 @07:40AM (#31860313)
They're usually edge cases. For example let-chains changed the parsing logic for if-let constructs across all editions.

I expect these to become even less frequent with ever rising amounts of Rust code that isn't on Github.