Oh, that - people serious about making C++ code limp along have known this for years. Valgrind won't work without the $FORCE_NEW variables.
#Rust compiler shows failings of ownership-based resource management & gets cursed, where C++ smart pointers crap out silently & get praised
-
-
This Tweet is unavailable.
-
- 2 more replies
-
-
-
Can you elaborate on this? Links? Articles?
-
Make a graph (Node keeping Node*, cycles.) Rust: compiler error, use indexes. C++: shared_ptr (leaks), T*/other_smart_ptr (manual=buggy)
- 1 more reply
New conversation -
-
-
The messenger gets shot.
-
I don't mind "Rust bans it but I think I can write this and iron out the bugs." It's "C++ smart pointers make my code bug-free" that gets me
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.