News for hackers. Stuff that matters.
Re:11 year old unsoundness bugs found in Rust borrow checker by bluGill on Tuesday October 13, 2026 @10:57AM (#50072756)
The reality though it many people are not using smart pointers. I have seen many people argue they don't like them because they want to see every place delete is called. (meanwhile of course they never notice all the places it should be called but isn't - but at least where it is they see it)
Re:11 year old unsoundness bugs found in Rust borrow checker by bayindirh on Tuesday October 13, 2026 @11:16AM (#50073046)
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.

Re:11 year old unsoundness bugs found in Rust borrow checker by thayne on Tuesday October 13, 2026 @11:50AM (#50073649)
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.
Re:11 year old unsoundness bugs found in Rust borrow checker by LeSaucy on Tuesday October 13, 2026 @12:26PM (#50074323)
smart pointers solve a different problem than data races
Re:11 year old unsoundness bugs found in Rust borrow checker by thayne on Tuesday October 13, 2026 @02:17PM (#50076164)
That's my point. C++ doesn't have an equivalent of rust's protections around Send and Sync.
Re:11 year old unsoundness bugs found in Rust borrow checker by IcyWindows on Tuesday October 13, 2026 @08:33PM (#50080916)
Won't those same people just use unsafe in Rust?

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