[D-runtime] Committed and uncommitted memory in the GC

[Sean Kelly]

On May 30, 2013, at 3:45 AM, Rainer Schuetze <r.sagitario at gmx.de> wrote:
> 
> Considering that (apart from very large user allocations that need committed memory anyway) the maximum pool size is currently only 32 MB (though I think this should be configurable), it doesn't make much sense to me to distinguish between committed and uncommitted memory. It is probably also more efficient to allocate committed memory than to commit it in separate steps for every 64kB.
> 
> According to the repo-history Sean is the author of that code, so he might have good use cases for uncommitted memory.

I think some form of that code has always been there.  If I had any goal in preserving it it was just to use only as much main memory as needed.