▲ 731 ▼ Supreme leader mad (sh.itjust.works) submitted 2 years ago by 0x4E4F@sh.itjust.works to c/linuxmemes@lemmy.world 101 comments fedilink hide all child comments
[–] nandeEbisu@lemmy.world 3 points 2 years ago (1 child) I don't think its the ergonomics of the language he has an issue with. If anything C++1x probably just made the original critiques of bloat worse. permalink fedilink source parent hideshow 2 child comments replies: [–] ozymandias117@lemmy.world 13 points 2 years ago (1 child) 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/e5949a27-999d-4b6e-8c49-3dbed32a00bc@zytor.com/ 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 permalink fedilink source parent hideshow 2 child comments replies: [–] nandeEbisu@lemmy.world 1 point 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] ozymandias117@lemmy.world 2 points 2 years ago* (last edited 2 years ago) (1 child) 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 permalink fedilink source parent hideshow 2 child comments replies: [–] nandeEbisu@lemmy.world 2 points 2 years 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. permalink fedilink source parent
[–] ozymandias117@lemmy.world 13 points 2 years ago (1 child) 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/e5949a27-999d-4b6e-8c49-3dbed32a00bc@zytor.com/ 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 permalink fedilink source parent hideshow 2 child comments replies: [–] nandeEbisu@lemmy.world 1 point 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] ozymandias117@lemmy.world 2 points 2 years ago* (last edited 2 years ago) (1 child) 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 permalink fedilink source parent hideshow 2 child comments replies: [–] nandeEbisu@lemmy.world 2 points 2 years 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. permalink fedilink source parent
[–] nandeEbisu@lemmy.world 1 point 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] ozymandias117@lemmy.world 2 points 2 years ago* (last edited 2 years ago) (1 child) 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 permalink fedilink source parent hideshow 2 child comments replies: [–] nandeEbisu@lemmy.world 2 points 2 years 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. permalink fedilink source parent
[–] ozymandias117@lemmy.world 2 points 2 years ago* (last edited 2 years ago) (1 child) 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 permalink fedilink source parent hideshow 2 child comments replies: [–] nandeEbisu@lemmy.world 2 points 2 years 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. permalink fedilink source parent
[–] nandeEbisu@lemmy.world 2 points 2 years 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. permalink fedilink source parent
