this post was submitted on 13 Apr 2024
730 points (95.9% liked)

linuxmemes

20880 readers
5 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 13 points 7 months ago (1 children)

In that post, his critiques were around the problems with the STL and everyone using Boost. The STL has improved significantly since then, and it would be a limited subset of c++ if it was ever allowed

There have been mailing list conversations earlier this year, citing that clang/gcc now allowing c++ in their own code might mean they’ve taken care of the issues that made it unusable for kernel code

https://lore.kernel.org/lkml/[email protected]/

I’m not saying it will happen, but it’s not being shot down as an absolute insanity anymore, and I wouldn’t have expected Rust to be allowed in the kernel, either

[–] [email protected] 1 points 7 months ago (1 children)

Oh interesting. I didn't realize boost was the main issue. Most people I've talked to were complaining about VTables introducing a bunch of indirection and people blindly using associative containers.

[–] [email protected] 2 points 7 months ago* (last edited 7 months ago) (1 children)

Vtable equivalents are used extensively in the kernel

You’ll find structs all over the place setting them up, e.g. every driver sets up a .probe function that the core will call, since it doesn’t know what driver it’s loading

[–] [email protected] 2 points 7 months ago

Right the issue was more because they're so easy to throw in without thinking about it so people overuse them. That may just be older devs complaining about newbies though.