Re: GC.forget() (Was: O(N) Garbage collection?)

2011-02-20 Thread Steven Schveighoffer
On Sat, 19 Feb 2011 22:39:10 -0500, Nick Sabalausky wrote: "bearophile" wrote in message news:ijpkh8$232r$1...@digitalmars.com... dsimcha: Yeh, I rebuilt the same model in my head over the past few hours (like you, I had a good mental model of the GC at one point but have slowly forgotten i

Re: GC.forget() (Was: O(N) Garbage collection?)

2011-02-19 Thread Nick Sabalausky
"bearophile" wrote in message news:ijpkh8$232r$1...@digitalmars.com... > dsimcha: > >> Yeh, I rebuilt the same model in my head over the past few hours (like >> you, I had a good mental model of the GC at one point but have slowly >> forgotten it). > > For serious D programmers having such model

Re: GC.forget() (Was: O(N) Garbage collection?)

2011-02-19 Thread bearophile
dsimcha: > Yeh, I rebuilt the same model in my head over the past few hours (like > you, I had a good mental model of the GC at one point but have slowly > forgotten it). For serious D programmers having such model in the head is so important that I'd like a short page with such explanations &

Re: GC.forget() (Was: O(N) Garbage collection?)

2011-02-19 Thread dsimcha
...and actually, forget() would only work for arrays of primitives, because if the object has pointers, you can change what these point to after calling forget() and Bad Things Can Happen. On 2/19/2011 6:17 PM, dsimcha wrote: Yeh, I rebuilt the same model in my head over the past few hours (li

GC.forget() (Was: O(N) Garbage collection?)

2011-02-19 Thread dsimcha
Yeh, I rebuilt the same model in my head over the past few hours (like you, I had a good mental model of the GC at one point but have slowly forgotten it). Unfortunately it looks like there's no easy fix. It also seems like gcbits are allocated as 1 bit for every 16 bytes of heap space, no ma