This is still generational GC but with a young generation heap per coroutine. I've been working on multi-heap GC for MRI Ruby. Compared to traditional concurre

This is still generational GC but with a young generation heap per coroutine. I've been working on multi-heap GC for MRI Ruby. Compared to traditional concurrent generational GC, skipping the marking when a coroutine terminates is not really an advantage because there will be no live objects to mark and marking would immediately terminate anyway. After that, you just reset the nursery pointer and you're done.