Hi,

At Sat, 26 Sep 2009 05:18:02 +0900,
Charles Oliver Nutter wrote in [ruby-core:25769]:
> Functionally, this works just fine, other than the cost of us spinning
> up a thread. But there's a larger problem: an Enumerator-created
> thread has a full lifecycle apart from the caller's thread. As a
> result the enumerator thread can root objects (preventing them from
> being GCed), including the Enumerator itself.

Why does the enumerator thread make the Enumerator marked?

-- 
Nobu Nakada