Anyone claiming they can write memory safe / defined C code at scale either has no experience with it or has their head buried in the sand.
Use-after-free and double-free shouldn't be able to happen unless you're doing really bad things.
-
-
They do happen in all real world C projects of non-trivial size though. Even when abstracting most forms of lifetime management.
-
They even happen all over the place in C++ with zero manual memory management. End up with complex references between things.
-
That's because C++ is too complex it be usable.
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.