“Mozilla could have achieved 90% of what it wanted from a rust rewrite with a modern C++11 rewrite at a quarter of the cost.” #shithnsays
-
-
I readily acknowledge that modern C++ is good at preventing *leaks*, but those aren’t what we’re worried about.
-
At some point in the 90s people started informally treating the term “memory leak” interchangeably with “memory safety problem” and I think that caused a lot of misconceptions.
- 5 more replies
New conversation -
-
-
Many modern C++ constructs encourage and mask use-after-free. Using destructors for managing all resources while still using references, iterators, etc. makes that worse, not better. Features like string_view are going to amplify that even further. It mostly helps avoid leaks...
-
Destructors are great in a type / memory safe language, but it's even easier to create dangling references when destruction is implicit rather than explicit. I've spent a lot of time debugging these memory corruption bugs and it's so much worse to resolve with C++ than C.
- 1 more reply
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.