Explicit memory deallocation

[Jarrett Billingsley]

"Neil Vice" <psgdg at swiftdsl.com.au> wrote in message 
news:fr3k2v$30ss$1 at digitalmars.com...

> "disable() temporarily disables garbage collection cycle, enable() then 
> reenables them."
>
> Given this I suspect that the GC still expects to be in control of memory 
> so even though the GC thread may not be running dynamically freeing 
> things, constructor calls will still register pointers with the GC and 
> expect some sort of internal consistency you are breaking with explicit 
> destroys perhaps...

The current GC implementation that D uses (no matter what library you're 
using) is synchronous, that is, it does not run in a separate thread.  GC 
collections will only happen on memory allocations.  When the GC is 
disabled, it should not perform any collections.