Re:Memory safety CVEs differ between Rust and C/C++
by vouwfietsman on Monday June 15, 2026 @02:12PM
(#48545020)
Knowing little about cpp modules and nothing about Gabriel Dos Reis, I expect a more design-by-committee type explanation for the result: the module system was probably a victim of having to be backwards compatible, abi stable, idiomatic, zero cost abstraction, be compatible with all weird cpp features, not hurt compile time, etc etc etc
I don't think its fair to attribute it to lack of skills or bad intent, unless there's some proof to any of it.
Re:Memory safety CVEs differ between Rust and C/C++
by reallyinchaos on Monday June 15, 2026 @02:13PM
(#48545038)
Nice try, Gabriel.
Re:Memory safety CVEs differ between Rust and C/C++
by jooops1 on Monday June 15, 2026 @02:50PM
(#48545448)
Yep I agree C++ lacks many features Rust has solid support for. But the real issue with C++ is the development process, almost all the people involved in the Module system are rather old and worked for Microsoft once. They are just in their own bubble and not having an open RFC-process blocks experts in that field.
C++ also does not have pattern matching, which is wildly popular in Rust.
Ladybird in the past used Swift apart from C++, but abandoned it. Swift has some peculiar issues, some of which might not be fixed over time. Ladybird's LLM-based conversion to Rust is interesting. I don't know much much unsafe the converted code has.