This is very cool, also I wonder does fugc works without InvisiCap, what would it be like without the capability pointer, does it just became not accurate but still usable?

I skimmed the article.

I'm curious about CPU / RAM overhead tradeoffs.

IE, in may cases GC is more CPU efficient than reference counting, but the tradeoff is higher RAM consumption.

Can anyone explain how the roots are known to the GC, I can't spot it. Does it have some kind of precompile step to mark roots for GC scan?

@pizlonator ?

Why did you choose to use an advancing wavefront rather than retreating wavefront strategy?

I'm amazed by how readable the source is, the names meaningful and not filled with jargon.

The description left me confused. Is this something that has to be integrated into the compiler?

Related, this is the Python garbage collector episode:

https://www.podscan.fm/podcasts/corepy/episodes/episode-21-a...

I found it very interesting.

How hard would it be to add generational collection?

wow, this is really fugcing cool

Oh this is so cool