Comment guardrails are for unexperienced developers (Score 1) 160
If you are a skilled c++ developer with 10+ years of experience you can most of the time write code that does not leak nor it corrupts your memory, and when you make a mistake with tools like the clang address/leak sanitizer, valgrind or the visual studio thing described in the article you can solve them... even on complex code bases written by other developers.
But if you have a junior engineer or also a senior one that does not know c++ in your team... even reviewing very cerefully his code it will be really hard to avoid those errors in your codebase...
This is where rust shines, since the junior developer (or the senior that does not know rust) will be stopped by the borrow checker, that will not only avoid memory leaks/corruptions and multithread issues (far harded to debug), but it will also enforce the use of a sane design-pattern in the code (many anti-pattern do not compile at all in rust...)