Hacker News Reader

Personally I love to use smart pointers where bleeding edge performance is not necessary.

If I need the absolute fastest code, then that code will be tortured under valgrind. That’s non-negotiable in my book.

Code is not done until its memory management is proven correct.

It's more than that. Smart pointer help, but there are cases where even when using smart pointers you can encounter memory safety issues. Especially when you need to interact with c or older c++ code that doesn't use smart pointers. And smart pointers don't provide any protection against data races in multi-threaded code, like rust does.

smart pointers solve a different problem than data races

That's my point. C++ doesn't have an equivalent of rust's protections around Send and Sync.

Won't those same people just use unsafe in Rust?

If not, why would they be allowed to do the same in C++