3 ms·

I pretty frequently argue that memory safety (etc) outcomes in modern C++ are pretty comparable to Rust, but that’s only true if you’re throwing clang-tidy, -We

I pretty frequently argue that memory safety (etc) outcomes in modern C++ are pretty comparable to Rust, but that’s only true if you’re throwing clang-tidy, -Werror, -Wall, -Wpedantic, and CI under ASAN, MSAN, UBSAN, TSAN. That’s pretty close to rustc. And I get that you can’t throw that at a giant codebase in one day, and I get that dev builds probably drop —Werror. Thrrr are realities. But new stuff not under clang-tidy, cppcheck, and pvs if you’re feeling speedy? People do that?

AlotOfReading 3y ago
That's simply not true. All of those tools are regularly used by large projects like chrome and have been for years. Memory safety continues to be the largest source of issues for them in spite of that. Sanitizers and other modern tools are a fantastic improvement over the old way of doing things, but they don't catch everything and we shouldn't pretend they do.