Garbage collector memory leak "feature"?

[0ffh]

More comments on what

Steven Schveighoffer wrote:
> 1. Is this just the way all garbage collectors are?  Is there not a way to 
> solve this problem?

No, only "conservative" gcs. There are also "exact" gc, but they have one
big drawback: No void* type at all is possible!
So either you want them, then you must use a conservative gc, or you don't
then you can have an exact gc.
D wants void*, so there is just no way round.

> 2. Does Tango have this problem?  I know the GC's are different, and I use 
> tango, so maybe I could just say, too bad for phobos users and be on my way 

Tango is D too, so it must have the same "problem".

> 3. If it is solvable, is anyone working on this?  If not, they should be. 
> Add this to the list of things that need to be fixed before D has widespread 
> adoption.  Memory leaks == bad bad bad.

It is not technically correct to call prudently retained memory blocks
a "memory leak". Those are distinct concepts, in my book at least.

Regards, Frank