News for hackers. Stuff that matters.
Re:C++26 Disapproved by uecker on Thursday November 05, 2026 @01:38AM (#50375923)
But this is always comparing apple and oranges: "theoretically, a user can completely avoid memory safety issue in Rust by never using unsafe or problematic dependencies" vs. "in practice C/C++ still often have memory safety issues".

In practice, we also still see memory safety issues also in Rust code because people use "unsafe" or have a dependency that does. I also see that practical impact of memory safety issues in well-maintained C/C++ code is almost zero for my personal security (rare, often mitigated or extremely difficult to exploit). I am far more scared about supply chain issues (and I bring this up as comparison for proper risk assessment, not to move away from memory safety).

Then, with more effort, and especially with "contracts", one could also make sure C/C++ have no memory safety issues. I have done this in small programs. The languages does not fully support this, yes, but why does this matter so much? The language / compiler still support reducing memory safety issues to low levels - which is relevant, because outside of theoretical scenarios, this is what Rust also does in practice (and not completely get rid of memory safety issues). And then now in this thread, this was even used as argument against a feature that would be a step towards full memory safety.

(I am not talking about compilers bugs).

There are no comments on this comment yet.