On 17/07/2013 12:33 PM, Jonathan S. Shapiro wrote: > > I suspect for prompt reclamation/finalization reasons. I think it > would > be quite surprising to many people if all of a task's resources aren't > immediately finalized as soon as it completes. Tracing introduces an > observable latency. > > > Nah. First, finalization is rare, and second, /correct/ finalization > does not (and /cannot/) require tracing.
I don't think we're on the same page. I'm not suggesting tracing is required, I'm suggesting that the expected task semantics includes prompt reclamation/finalization of resources. Ref counting provides this, tracing does not. Sandro _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
