[Vm-dev] Object age (was Re: first window, yay!)
asqueaker at gmail.com
Mon Sep 23 19:11:32 UTC 2013
>> Being able to enumerate in order of creation time is something the VM could maintain in old space, keeping objects in order there-in. But I'd rather drop this property and allow the Spur GC to compact using best-fit and lazy become, which will change the order of objects. How important is being able to enumerate in order of creation? I think it's nice to have but hardly essential. What do y'all think?
Any application that would care about it would not rely on some lucky
implementation side-effect, it would solve the ordering requirement
explicitly by its own code.
More information about the Vm-dev