29 ms·
> Avoiding dangling references is another part of memory safety, and GC is one way to accomplish that; it's not orthogonal. It's the removal of the `free` and
by Arelius 13y ago
> Avoiding dangling references is another part of memory safety, and GC is one way to accomplish that; it's not orthogonal.
It's the removal of the `free` and `delete` semantics that avoid dangling references. Not GC. While GC posits a good alternative to many of these problems. GC doesn't actually help memory safety at all. Unless you consider memory leaks to be a matter of "memory safety".
- rbehrends 13y agoAvoiding premature free()s is precisely what garbage collection accomplishes in this context, because you will never have to call free() to avoid running out of memory.