News for hackers. Stuff that matters.
Re:Upcoming Rust language features for kernel development by hannesfur on Thursday October 16, 2025 @04:21AM (#45602781)
These seem like the first features that Rust in Linux bring to the Rust language that are not almost exclusively useful to the kernel. In my perception the focus on bringing features for the kernel has held up development in other parts of the language and the standard library.
Re:Upcoming Rust language features for kernel development by oersted on Thursday October 16, 2025 @04:46AM (#45602939)
As I understand it systems programming is the priority application area for Rust, and there are plenty of projects working on OSs, embedded or other bare-metal cases, as well as interoperability with complex C codebases.

At first glance, these features look quite general to me and not particularly tied to the kernel, they are important utilities for doing this kind of programming in the real world.

Re:Upcoming Rust language features for kernel development by heavyset_go on Thursday October 16, 2025 @05:50AM (#45603401)
What's the story with C interop now with these and related changes? I'm out of the loop.
Re:Upcoming Rust language features for kernel development by muvlon on Thursday October 16, 2025 @06:48AM (#45603823)
C interop is excellent and has been for years. The one piece that still needs unstable is defining/exposing varargs functions (support for calling them was stabilized many years ago). You can write almost anything you can write in C in (partly unsafe) Rust, in fact there are projects like c2rust that automate this translation.

These new features are all about making things that the kernel devs need possible in safe Rust. This often requires support for some quite fancy abstractions, some of which cannot be expressed in current stable Rust.

Re:Upcoming Rust language features for kernel development by Foxboron on Thursday October 16, 2025 @08:24AM (#45604477)
> C interop is excellent and has been for years.

Only if you primarily work with `cargo` and want to interact with C from Rust. The other way around has far less support and `rustc` does not standardize the object generation. This is actively preventing projects like `systemd` to adopt Rust into their project as an example.

https://github.com/systemd/systemd/pull/19598

Re:Upcoming Rust language features for kernel development by aw1621107 on Thursday October 16, 2025 @09:53AM (#45605356)
> Only if you primarily work with `cargo` and want to interact with C from Rust.

In what way(s) does Rust's C interop depend on cargo?

> The other way around has far less support and `rustc` does not standardize the object generation.

I believe in this context the understanding is that you're going to be using `extern "C"` and/or `#[repr(C)]` in your Rust code, which gives you a plain C interface. I think attempting to use "raw" Rust code from other languages is a rare phenomenon, if it's even attempted at all.

> This is actively preventing projects like `systemd` to adopt Rust into their project as an example.

Could you point out specific instances from that thread? From a quick glance I didn't see any obvious instances of someone saying that using Rust from C is problematic.

Re:Upcoming Rust language features for kernel development by humanrebar on Thursday October 16, 2025 @11:55AM (#45606980)
> In what way(s) does Rust's C interop depend on cargo?

Do rust and cargo allow for multiple interpretations of the same C header file across different objects in the same program? That's how C libraries are often implemented in practice due to preprocessor tricks, though I wish it wasn't normal to do this sort of thing.

Re:Upcoming Rust language features for kernel development by nicoburns on Thursday October 16, 2025 @12:39PM (#45607574)
I would expect so. Rust and Cargo don't consume C header files directly at all. They consume bindings generated by bindgen (or hand written if you prefer). So you could probably generate mulitple bindings if you needed multiple interpretations of a C header.

If the header files are consumed by C code that is then consumed by Rust then you'll have full support for what C supports because it will be compiled by a C compiler.

Re:Upcoming Rust language features for kernel development by steveklabnik on Thursday October 16, 2025 @12:55PM (#45607775)
Rust and Cargo do not build C programs, so, the answer to that is "no", strictly speaking.

However, some people use cargo's build scripts to build c programs, which then you can link into your Rust program. Support would then depend on whatever the person wrote with the script, which in my experience usually delegates to whatever build system that project uses. So it should work fine.

Re:Upcoming Rust language features for kernel development by DaanDeMeyer on Thursday October 16, 2025 @03:21PM (#45609582)
https://github.com/rust-lang/rust/issues/73632 needs to be addressed and then integrated into meson before systemd could consider adopting rust.
Re:Upcoming Rust language features for kernel development by aw1621107 on Thursday October 16, 2025 @11:07PM (#45612962)
Thanks for the example!

I guess looking at that pedantically that's "just" a tooling issue, rather than an issue with the Rust language itself. That's not really a useful distinction from an end user's perspective, though; it's friction either way, and worth addressing.

Re:Upcoming Rust language features for kernel development by namr2000 on Thursday October 16, 2025 @10:06AM (#45605535)
I have to disagree here a little bit. Calling C functions from Rust is a very pleasant experience, but the other way around is not so nice. You usually have to manually create types that will unpack rust collections into C compatible structures (think decomposing `Vec` into ptr, len, capacity) & then ensure that memory passed between the two sides is free'd with the appropriate allocator. Even with `cbindgen` taking care of the mindless conversions for you, you still have to put a lot of thought into the API between the two languages.

I am currently working on a fairly involved C & Rust embedded systems project and getting the inter-language interface stable and memory-leak free took a good amount of effort. It probably didn't help that I don't have access to valgrind or gdb on this platform.

Re:Upcoming Rust language features for kernel development by aw1621107 on Thursday October 16, 2025 @10:19AM (#45605666)
I feel this might come down to the scope one has in mind when thinking of the word "interop". I think one can reasonably simultaneously claim that the interop "mechanics" are excellent in that it's generally possible to create a Rust library that quacks like a C library and that basically any C library is usable by Rust code, but the interop "ergonomics" are suboptimal in that (as you say) actually writing the glue code can be a bit of an adventure.
Re:Upcoming Rust language features for kernel development by namr2000 on Thursday October 16, 2025 @10:26AM (#45605767)
I think that's a fair assessment. To your point `cbindgen` makes the mechanics of the whole thing painless & linking was trivial. That's worth a lot especially when compared to other languages.
Re:Upcoming Rust language features for kernel development by heavyset_go on Thursday October 16, 2025 @07:11PM (#45611775)
Cool, thanks for the clarification
Re:Upcoming Rust language features for kernel development by 3836293648 on Thursday October 16, 2025 @08:52AM (#45604713)
It's C++ that is problematic, C has been easy for years
Re:Upcoming Rust language features for kernel development by heavyset_go on Thursday October 16, 2025 @07:07PM (#45611753)
Are the kernel-related changes applicable to C++ interop? Honest question, I don't know.
Re:Upcoming Rust language features for kernel development by gpm on Thursday October 16, 2025 @07:56PM (#45612065)
The kernel doesn't use any C++, so no more than incidentally.

There is some C++/rust interop in the past that I've worked on that would have enjoyed the arbitrary self types feature, but not particularly because of the C++ part of the equation. In fact I think if it had been a pure rust project it would also have enjoyed that feature just as much so... eh... take it for what little it's worth I guess.

Re:Upcoming Rust language features for kernel development by cyphar on Thursday October 16, 2025 @11:00AM (#45606233)
Calling C code from Rust? Pretty nice.

Writing Rust code to be called from C (but within the same application)? Doable but somewhat painful.

Writing Rust code to act like a C shared library? Quite painful and some pretty important features are missing (proper symbol versioning support being the most obvious one). Theoretically doable if you're willing to compromise.

There's also some aspects of FFI-safety that are very subtle and easy to mess up:

  * #[repr(C)] enums still have the same requirements as Rust enums and so C callers can easily trigger UB, so you need to use something like open_enum. Thankfully cbindgen is too dumb to know that #[open_enum] is a proc macro and produces a non-enum type.
  * Before io_safety in Rust 1.63, dealing with file descriptors from C without accidentally closing them was horrific (though this was a wider problem in Rust). BorrowedFd is quite nice -- though Rustix will panic if you use negative fds and so you need to add validation and your own type in practice. However, #[repr(transparent)] is very nice for this.
  * Lots of reading about unsafe Rust is necessary when doing most non-trivial things with C FFI.
  * You need to make use of a lot of compiler internals, build scripts, and other magic to get the output you want.
  * Tools like cargo-c and cbindgen are nice and probably work great for 80% of projects, but the 20% really suffer from no useful tooling. I haven't tried to use rustc directly to work around some of the remaining issues, but I suspect it'd be even more painful.
I would say that the C interop with Rust is pretty good but it has lots of room for improvement and it feels like very few resources have been spent on it after they got the core stuff working.

Source: I've been writing a Rust library intended to be used primarily via C FFI and run into a lot of issues...

Re:Upcoming Rust language features for kernel development by heavyset_go on Thursday October 16, 2025 @07:10PM (#45611774)
Thanks for the info, I've been wanting to use Rust in a project with a lot of FFI going both Rust <-> C ways. Still sounds like it's a bit hairy.
Re:Upcoming Rust language features for kernel development by pjmlp on Thursday October 16, 2025 @05:12AM (#45603117)
I see Rust's place on low level systems programming, for everything else on userspace compiled managed languages are a much better option, systems following an architecture like Self, Inferno or Android, so I don't see a big deal with these efforts focusing on low level C like capabilities.
Re:Upcoming Rust language features for kernel development by timschmidt on Thursday October 16, 2025 @05:23AM (#45603198)
> for everything else on userspace compiled managed languages are a much better option

As someone who's written a number of userspace applications in many languages as well as embedded firmwares running on bare metal, Rust is a rare gem that excels at both.

Re:Upcoming Rust language features for kernel development by pjmlp on Thursday October 16, 2025 @05:31AM (#45603251)
Only if those userspace applications are headless, Rust exceling at GUIs is a bit of a strech.
Re:Upcoming Rust language features for kernel development by timschmidt on Thursday October 16, 2025 @05:34AM (#45603280)
Well https://github.com/timschmidt/egui-rad-builder has come together rather well in the last week of hacking, if I say so myself. I think building a similar app with QT, for example, would have been significantly more challenging.

I'm particularly fond of how easy it was to make all the controls live in the editor, and editable with changes appearing immediately. imgui would probably provide a similar experience, but I find C++ much more of a pain to work with than Rust.

Re:Upcoming Rust language features for kernel development by pjmlp on Thursday October 16, 2025 @06:07AM (#45603528)
How does it handle localization and assistive technologies, UI/UX tooling for designers, 3rd party component ecosystem?
Re:Upcoming Rust language features for kernel development by timschmidt on Thursday October 16, 2025 @06:43AM (#45603790)
egui works with AccessKit to provide accessibility support. I haven't added anything explicitly to the RAD builder for it yet. Great idea!
Re:Upcoming Rust language features for kernel development by ogoffart on Thursday October 16, 2025 @06:25AM (#45603673)
Regarding Rust GUI framework, there is also Slint https://slint.dev

(Disclaimer: I'm one of the Slint developers.)

Re:Upcoming Rust language features for kernel development by timschmidt on Thursday October 16, 2025 @06:47AM (#45603811)
I looked at Slint a couple years ago when I was evaluating UI toolkits. Looks slick! The only thing that turned me off was needing an additional DSL to define UIs. Trying to learn fewer languages, more deeply, these days. Is it possible to use Slint without the DSL?
Re:Upcoming Rust language features for kernel development by ogoffart on Thursday October 16, 2025 @07:03AM (#45603918)
Slint does require using its DSL to define UIs, but I'd argue it's not really like learning a whole new language. It's not harder than learning the API surface of any other GUI framework.

I actually wrote a blog post about this exact topic, since it's a common question: https://slint.dev/blog/domain-specific-language-vs-imperativ...

Re:Upcoming Rust language features for kernel development by onionisafruit on Thursday October 16, 2025 @07:45AM (#45604211)
That’s a compelling post. You drew me in by calling SQL a DSL. You’re right, but if you asked me to list the DSLs I use regularly I never would have thought of SQL until now. My thinking was too uptight because I didn’t consider the “domain” in DSL could be something as big as querying structured data. That makes me wonder if Rust is a DSL for the domain of general computing (obviously not in the usual intended meaning of DSL).

Like the person you’re replying to, I am generally averse to DSLs where the domain is a single project because I associate them with previous bad experiences where I spent time learning only to find it totally misses the mark. There’s also the issue of software where I’m the sole maintainer and look at it rarely. If it’s the only place I use Slint, then I’m going to be worried that I need to relearn the DSL in three months when I want to tweak the UI. Although you can probably say the same about any non-trivial framework’s API whether or not it uses a DSL.

All that said, I’ll be a bit more open to DSLs after reading your post, and if I ever need to write a GUI in Rust I’ll give Slint a shot (although that seems unlikely since I don’t typically write Rust or GUIs).

Re:Upcoming Rust language features for kernel development by timschmidt on Thursday October 16, 2025 @07:15AM (#45603998)
I appreciate the answer, and you taking time to write up your thoughts on it. Your point about the GUI builder working with the DSL is noted. In the egui RAD builder, I am manipulating structs which describe the UI (and which can be exported / imported as JSON) prior to code generation, which amounts to something similar. I still feel I have to context switch less, the back-and-forth is of more concern to me than learning an additional language.

That said, great work! There's plenty of room in the language for more than one solution!

Re:Upcoming Rust language features for kernel development by codedokode on Thursday October 16, 2025 @09:26AM (#45605083)
I don't think the DSL is any good. It looks weird (like a mix of CSS and classes), and it has a side effect of locking the user to a specific product.

In your article, you mention that an imperative code in Rust looks more complicated, but this can be fixed by adding an "object tree" syntax to Rust, that allows creating trees of objects and link them like this:

    VBox margin=10:
        Label text=label_text 
        Button label="OK" onclick=on_ok_clicked
This syntax could be used not only for UI, but for describing configuration, database tables and many other things. I think it would be better solution than a proprietary language.

Also I think it would be better if GUI could be drawn in the editor, it would allow to use lower paid developers without expensive computer science education for making UI.

Re:Upcoming Rust language features for kernel development by yencabulator on Thursday October 16, 2025 @07:44PM (#45611998)
Re:Upcoming Rust language features for kernel development by shakow on Tuesday October 21, 2025 @06:42PM (#45662660)
God forbid a company plays the GPL rules fair and square...
Re:Upcoming Rust language features for kernel development by yencabulator on Tuesday October 21, 2025 @07:05PM (#45662893)
Even FSF makes their central libraries LGPL not GPL.
Re:Upcoming Rust language features for kernel development by mdhb on Thursday October 16, 2025 @05:48AM (#45603391)
But that’s no longer the choice you need to make. Ubuntu themselves have said for a couple of years now that every new GUI app they make natively for Linux is going to be Flutter and dedicated a bunch of engineers to the project to make sure it’s a first class citizen.

Beyond that, Dart / Futter are truly an absolute pleasure to use for that use case.

Re:Upcoming Rust language features for kernel development by johnisgood on Thursday October 16, 2025 @06:28AM (#45603695)
Yeah, I do not know Dart / Flutter much, but if I had to choose, I would either pick that, or wxWidgets, or even Tcl/Tk, but not Rust.
Re:Upcoming Rust language features for kernel development by timschmidt on Thursday October 16, 2025 @05:54AM (#45603432)
Sounds great for the Dart people. But unrelated to correcting misinformation about Rust. I'm not opposed to whatever language folks want to use. Just out here hacking in Rust because it suits my particular needs. And finding that it's enjoyable to hack GUIs as well as firmwares in.
Re:Upcoming Rust language features for kernel development by mdhb on Thursday October 16, 2025 @06:00AM (#45603488)
No I get all that, but to the parent comments point however, there’s no way in hell I would ever pretend for a moment that one is as straightforward as the other and it’s no longer a choice between Rust and C++ both of which add a lot of complexity to a scenario where it offers very little benefit.
Re:Upcoming Rust language features for kernel development by timschmidt on Thursday October 16, 2025 @06:05AM (#45603514)
Over the years, I've found that the complexity is there whether or not it's been papered over by a runtime. It's wonderful to forget about, until it's not. Some applications may never run into the limitations imposed by abstracting it away, but others run into them quickly.

"There ain't no such thing as a free lunch" as the saying goes.

Re:Upcoming Rust language features for kernel development by mdhb on Thursday October 16, 2025 @06:12AM (#45603566)
To which the counter argument I guess would be.. there’s no sense in trying to solve for some abstract future set of problems that the vast majority of people are never going to have ahead of time on the off chance you’re one of them.

That too requires a substantial investment of time and resources.

I think in a more pragmatic sense too that you can form a very good understanding on if you’re going to have weird special requirements just from looking at what others have done with the same tools in similar situations before you.

Re:Upcoming Rust language features for kernel development by timschmidt on Thursday October 16, 2025 @06:21AM (#45603643)
> there’s no sense in trying to solve for some abstract future set of problems that the vast majority of people are never going to have

> That too requires a substantial investment of time and resources.

The discussion has gotten to be pretty abstract at this point. To get back to concrete examples, the egui RAD builder I've been hacking on worked on day 1, first commit. It's been a joy to put together, and no more difficult than building GUI apps with any other toolkit I've worked with. Which causes me to question your statements about additional complexity. You can dig deep and do dark magic with Rust if you want, but you can also treat it like any high level language and get things done quickly. That's part of what makes it a rare gem to me.

Some folks don't like dealing with strict types, or with the borrow checker, but I find that the errors they illuminate for me would have been similarly serious in other languages which lacked the tooling to highlight them. Which adds to my appreciation of Rust.

Re:Upcoming Rust language features for kernel development by izacus on Thursday October 16, 2025 @08:53AM (#45604730)
One week of hacking makes every library look good, but have you shipped actual product that other people widely use with Rust GUI yet? What was the experience there and - most importantly - what were the downsides?
Re:Upcoming Rust language features for kernel development by timschmidt on Thursday October 16, 2025 @08:59AM (#45604785)
I've been working with egui for a couple years. Written maybe a dozen applications with it doing various things from image manipulation to 3D graphics. As I've said elsewhere in the thread, I haven't run into anything I wasn't able to accomplish with it.

Immediate mode has it's detractors, but in practice I've found it remarkably flexible, the resulting code relatively clean, and egui gets out of the way when I want to do something like blit fast graphics to a memory mapped area of the screen. Responses have been positive.

Re:Upcoming Rust language features for kernel development by cosmic_cheese on Thursday October 16, 2025 @06:51AM (#45603840)
Indeed. Last I knew all the Rust UI libraries were declarative and/or immediate mode, both of which have their place but I’m not convinced that they’re suitable in all situations. Sometimes you need a boring “old style” imperative UI framework with deep toolbox of capable widgets (think AppKit, win32, etc), but that’s notably absent in the Rust world.
Re:Upcoming Rust language features for kernel development by timschmidt on Thursday October 16, 2025 @06:53AM (#45603857)
https://www.gpui.rs/ is a relatively new entrant which is described as "hybrid immediate and retained mode". Maybe worth checking out for your use cases.

Immediate mode was certainly a different paradigm to wrap my head around, but so far I haven't found anything I couldn't accomplish with egui, including some fairly complex applications like https://timschmidt.github.io/alumina-interface/

Re:Upcoming Rust language features for kernel development by timeon on Thursday October 16, 2025 @07:10AM (#45603955)
How far from "old style" is Slint?
Re:Upcoming Rust language features for kernel development by cosmic_cheese on Thursday October 16, 2025 @10:44AM (#45605996)
From a quick glance, about as far as the other Rust toolkits. Looks declarative with with a relatively small number of more basic widgets (a lot of custom widget code is necessary), as opposed to e.g. AppKit which is imperative and comes with a great number of rich widgets that are ready to use out of the box.
Re:Upcoming Rust language features for kernel development by IshKebab on Thursday October 16, 2025 @07:43AM (#45604194)
Sure, but that's true of basically every language except maybe C++, C#, Javascript/Typescript and Dart.

GUIs are incredibly hard and most languages never get high quality GUI libraries. Rust is still pretty young and a ton of people are working on the problem so that will definitely change.

Re:Upcoming Rust language features for kernel development by afishhh on Thursday October 16, 2025 @08:57AM (#45604766)
> Rust exceling at GUIs is a bit of a strech.

I strongly agree with this. In particular the Rust GUI libraries I've looked at have text layout / rendering that is nowhere near what should be considered adequate today (imo).

For example egui:

- It doesn't do any bidi reordering.

- It also doesn't do any font fallback so even if you didn't need bidi you can't render many languages without first acquiring an appropriate font somehow.

- Complex shaping is nowhere to be seen either.

- egui's italics look really terrible and I'm not sure why since I can't believe even synthesized ones have to look that bad.

CSS has been doing this for years and it's been doing it very well. So I am kind of disappointed that we don't have equally powerful tools in the general Rust ecosystem. Even just considering text layout / rendering libraries, only `cosmic-text` has an API that is somewhat in the right direction[1], but even it fails simply because I don't see a way to insert a button (block element) in-between the text[2].

Note that I'm not just hating on egui here, egui is amazing. Afaict it is the most complete GUI library for Rust and it's great to be able to make GUIs this easily. However I can't just not point out that it is, in fact, not perfect and doesn't truly "excel" at GUIs.

Also I have no idea how inline layout looks in other established GUI libraries like GTK and Qt so maybe I'm complaining about something that is not available most places outside a browser. If anyone knows, it would be interesting to learn how well they compare here.

[1] CSS inline layout is so complex that even this is a decent achievement, since it is not reasonable to expect most CSS features out of new Rust libraries with a significant time disadvantage.

[2] This is non-trivial because bidi reordering should happen on the whole paragraph not only on both sides of the button, so the inline layout API must handle non-text blocks in text.

Re:Upcoming Rust language features for kernel development by timschmidt on Thursday October 16, 2025 @09:40AM (#45605211)
This is a detail oriented list of real issues, which is wonderful! ChatGPT found open issues in the egui Github for each of your problems, so they're known about and being worked on.

However, it seems like most of the other UI toolkits discussed here, even in other languages, suffer similar issues. Which points to the difficulty of the problems. Consequently, I don't have any problem praising egui and Rust alongside. They're great! And even great can always get better! :)

Re:Upcoming Rust language features for kernel development by mamcx on Thursday October 16, 2025 @11:04AM (#45606274)
> Rust exceling at GUIs is a bit of a strech.

BTW, this happens to almost all languages. Which ACTUAL good GUIs toolkits exist? And which ACTUAL languages HAVE good integration or implementation of them?

A good GUI kit AND integration is a bigger task than do a Os or a RDBMS. (And neither are many good languages for RDBMS)

Re:Upcoming Rust language features for kernel development by 0x457 on Thursday October 16, 2025 @03:06PM (#45609414)
Depends on your definition of good.

I think Swift (and even ObjC) is perfect for AppKit & UIKit. I think those frameworks are pretty good and I like using them. Languages have great integration, Swift literally made around them. Those toolkits have great integrations with the macOS.

I find C# a pretty nice language for GUI, I assume it has good (maybe not great) integration with at least one of MS GUI toolkits.

I find Rust good for GUI, but right now story is meh. Wrapper style frameworks always suffer from Rust not being whatever it wraps. Pure Rust framework miss a lot of features compared to wrapper frameworks.

Re:Upcoming Rust language features for kernel development by pjmlp on Friday October 17, 2025 @02:31AM (#45613856)
Delphi, VB, Java, Kotlin, Dart, C#, VB.NET, Swift, Objective-C.

All of the above also have great ORM libraries and RDBMS standard driver APIs, as doing data entry applications is a common enterprise GUI workflow.

Re:Upcoming Rust language features for kernel development by mamcx on Friday October 17, 2025 @04:03PM (#45621356)
Well if that is what you call good from ORM (I agree Delphi for GUI, the others not so much).

A truly good one? FoxPro. Is very hard to know if you don't have exposure to what should be.

Re:Upcoming Rust language features for kernel development by anarki8 on Thursday October 16, 2025 @11:31AM (#45606633)
I wouldn't say it's bad at GUIs either. There are some nice libraries like Iced and Slint. Some even have good accessibility support like egui.

There is a full-fledged DE written in Rust that uses Iced: https://en.wikipedia.org/wiki/COSMIC_(desktop_environment)

Re:Upcoming Rust language features for kernel development by WD-42 on Thursday October 16, 2025 @11:32AM (#45606652)
The GTK bindings are fine.
Re:Upcoming Rust language features for kernel development by discreteevent on Thursday October 16, 2025 @05:38AM (#45603316)
> Rust is a rare gem that excels at both.

This can be true but it can still be the case that a managed language is even better at one of them.

Re:Upcoming Rust language features for kernel development by timeon on Thursday October 16, 2025 @07:04AM (#45603920)
> for everything else on userspace compiled managed languages are a much better option

Except for thread safety.

Re:Upcoming Rust language features for kernel development by pjmlp on Thursday October 16, 2025 @07:25AM (#45604061)
Fearless concurrency, is only fearless for a very fine grained version of it.

In memory resources shared among threads.

Turns out threads also may share resources like out-of-process files, memory mapped regions, shared memory, databases, distributed transactions,.... where the Send and Sync traits is of no help.

Also you happen to forget Haskell has a Software Transactional Memory, and Swift also has similar protocols since version 6, and effects are a thing in OCaml, Scala, Koka, while languages like Dafny, Koka and Idris also provide similar capabilities via proofs.

Re:Upcoming Rust language features for kernel development by okanat on Thursday October 16, 2025 @05:53PM (#45611143)
That's why everybody who cares about OS safety should invest into capability-based operating systems. They take the concept of Send and Sync and implement at the runtime of the entire computer.
Re:Upcoming Rust language features for kernel development by adwn on Thursday October 16, 2025 @07:37AM (#45604133)
> for everything else on userspace compiled managed languages are a much better option

That might be true if you're developing a pure application [1], but not if you're writing a library. Have fun integrating a C# library in a Java program, a Java library in a C# program, or either of those in a Python, Node, C, C++, or Rust program. There's something to be said for not requiring a runtime.

[1] Unless you care about easy parallelization with statically guaranteed thread-safety. But hey, who needs this in the age of multicore CPUs?

Re:Upcoming Rust language features for kernel development by pjmlp on Thursday October 16, 2025 @07:47AM (#45604221)
OS IPC exists for a reason, aren't microservices all the rage nowadays, and Plan 9 rules?
Re:Upcoming Rust language features for kernel development by adwn on Thursday October 16, 2025 @08:11AM (#45604369)
> OS IPC exists for a reason

Message-passing IPC is much, much slower and less efficient than shared-memory communication, and inter-process IPC (both message-passing and shared-memory) is much less convenient than intra-process multi-threading. Rust is the only mainstream language, managed or otherwise, which enables safe and efficient multi-threading.

Re:Upcoming Rust language features for kernel development by pjmlp on Thursday October 16, 2025 @08:32AM (#45604554)
Not at all, because as I explain on another sibiling answer, it is only safe if we cut down the use cases to a very specific one that helps to sell that narrative.
Re:Upcoming Rust language features for kernel development by pdimitar on Thursday October 16, 2025 @09:23AM (#45605058)
Eh, modern OS-es indeed have loads of problems still, of which non-transactional access to the filesystem is in my top three, but to put those problems on Rust is a bit uncharitable. It's not Rust's fault that zero kernel devs have the courage to finally start enforcing patterns that have proven themselves useful and safe for decades, in other areas outside of IT as well (i.e. in financial accounting).

Rust plucks the fruit it can reach and it mostly stays in its lane and it's trying to expand it here and there (like Rust in Linux and embedded). I too want one ultimate language and one ultimate kernel but I don't think you and I will live to see it. Maybe our grandchildren will not as well.

Re:Upcoming Rust language features for kernel development by adwn on Thursday October 16, 2025 @08:46AM (#45604671)
This one?

> Turns out threads also may share resources like out-of-process files, memory mapped regions, shared memory, databases, distributed transactions

For multi-threaded parallelization,

    - out-of-process files
    - databases
    - distributed transactions
aren't really relevant, and Rust directly helps with the other two aspects:

    - memory mapped regions
    - shared memory
In practice, your "very specific" aspect is the most important one, and the hardest to get right without Rust's Send and Sync traits and their automatic enforcement.
Re:Upcoming Rust language features for kernel development by pjmlp on Thursday October 16, 2025 @08:56AM (#45604754)
Who gets to say what is relevant is the architect driving the project implementation.

> aren't really relevant, and Rust directly helps with the other two aspects:

Not at all, because Rust code has nothing to say about what other processes do to those resources, the only thing you can do is wrap accesses in a unsafe code block and hope for the best, that nothing was corrupted.

Re:Upcoming Rust language features for kernel development by adwn on Thursday October 16, 2025 @10:53AM (#45606133)
I think you're confusing concurrency with parallelism. I've been talking about parallelization since my first comment in this thread. There's some overlap, yes, but the aspects you listed have typically very little to do with parallelization, which is why I called them "[not] really relevant". And where they do matter to multi-threading (the shared memory part), Rust does help with correctness.
Re:Upcoming Rust language features for kernel development by zacmps on Thursday October 16, 2025 @07:44PM (#45612001)
This is not the view everyone holds. For an example of work in the opposite direction see https://dioxus.notion.site/Dioxus-Labs-High-level-Rust-5fe1f....
Re:Upcoming Rust language features for kernel development by junon on Thursday October 16, 2025 @06:11AM (#45603563)
There are a lot of features being added for kernel/firmware development, they're just not on everyone's radar.

Philopp has been a particular force for change in this area.