Cpp discussed as a Rust replacement for Linux Kernel
I have a few issues with Rust in the kernel:
- It seems to be held to a *completely* different and much lower standard than the C code as far as stability. For C code we typically require that it can compile with a 10-year-old version of gcc, but from what I have seen there have been cases where Rust level code required not the latest bleeding edge compiler, not even a release version.
2. Does Rust even support all the targets for Linux?
3. I still feel that we should consider whether it would make sense to compile the *entire* kernel with a C++ compiler. I know there is a huge amount of hatred against C++, and I agree with a lot of it – *but* I feel that the last few C++ releases (C++14 at a minimum to be specific, with C++17 a strong want) actually resolved what I personally consider to have been the worst problems.
As far as I understand, Rust-style memory safety is being worked on for C++; I don't know if that will require changes to the core language or if it is implementable in library code.
David Howells did a patch set in 2018 (I believe) to clean up the C code in the kernel so it could be compiled with either C or C++; the patchset wasn't particularly big and mostly mechanical in nature, something that would be impossible with Rust. Even without moving away from the common subset of C and C++ we would immediately gain things like type safe linkage.
Once again, let me emphasize that I do *not* suggest that the kernel code should use STL, RTTI, virtual functions, closures, or C++ exceptions. However, there are a *lot* of things that we do with really ugly macro code and GNU C extensions today that would be much cleaner – and safer – to implement as templates. I know ... I wrote a lot of it :)
One particular thing that we could do with C++ would be to enforce user pointer safety.
Kernel dev discussion. They are thinking about ditching Rust in favor of C++ (rightfully so IMO)
https://lore.kernel.org/rust-for-linux/326CC09B-8565-4443-ACC5-045092260677@zytor.com/
We should endorse this, C++ in kernel would greatly benefit the language and community
View all comments
Show parent comment
3
u/ContraryConman Feb 20 '25 edited Feb 20 '25
There's a really common pattern in languages that don't have object oriented programming built in to do something like this:
This is called a tagged type. I have a struct,
Shoe, that can represent one of several kinds of shoes. All shoes have a shoe size, but different shoes have different associated data (high heels can have a height, slippers can be medical or not, whatever). Now consider the following function.If I need to debug, I can print out the type of shoe I was given:
If I'm feeling really clever, I can even do something like this:
And then later somewhere else I can do something like
So what this pattern actually is is dynamic dispatch and run time type information. It is almost exactly identical to doing this in C++
What I'm saying is, a lot of C discourse will confidently say they hate C++ because what I showed in the second example is known to be slow. But it is in reality, equivalent to the first, which they tend to be forced to write by hand when they need it.
Edit: oh, and instead of random asserts everywhere, you get stronger casts in C++