Smart pointers prevent leaks, not use after free. Borrow checking prevents use after free, not leaks. There's no meaningful memory safety unless you have both.
-
-
You still can have leaks with GC.
-
Some (not me, no never me) would argue that ref leaks aren't the same as true memory leaks, because they are still alive and used by something even if the author didn't intend for it to be the case. Of course there are more facets to the issue than that.
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.