Progress on the Gilectomy
Paul Rubin
no.email at nospam.invalid
Tue Jun 20 01:19:24 EDT 2017
Cem Karan <cfkaran2 at gmail.com> writes:
> Can you give examples of how it's not reliable?
Basically there's a chance of it leaking memory by mistaking a data word
for a pointer. This is unlikely to happen by accident and usually
inconsequential if it does happen, but maybe there could be malicious
data that makes it happen
Also, it's a non-compacting gc that has to touch all the garbage as it
sweeps, not a reliability issue per se, but not great for performance
especially in large, long-running systems.
It's brilliant though. It's one of those things that seemingly can't
possibly work, but it turns out to be quite effective.
More information about the Python-list
mailing list