Compile-time memory footprint of std.algorithm

[Peter Alexander via Digitalmars-d]

On Tuesday, 22 April 2014 at 18:09:12 UTC, Iain Buclaw wrote:
> Testing a 2.065 pre-release snapshot against GDC. I see that 
> std.algorithm now surpasses 2.1GBs of memory consumption when 
> compiling unittests.  This is bringing my laptop down to its 
> knees for a painful 2/3 minutes.

My (ancient) laptop only has 2GB of RAM :-)

Has anyone looked into why it is using so much? Is it all the 
temporary allocations created by CTFE that are never cleaned up?