Why counting CVEs to compare Rust and C++ is a trap, in one curl example (kobzol.github.io)
The author's claim: if a Rust function isn't marked unsafe, it's impossible to use incorrectly in a memory sense, so a memory bug there is always a soundness hole. C and C++ shift that burden to the caller, so the same class of mistake never becomes a CVE.
The thread split hard. One camp: CVE counts are so useless they ignore anyone citing them. Another, channeling Stroustrup: most of these bugs are C-style C++, and modern C++ plus hardened libraries closes the gap.
Sign in to save