Concern about dmd memory usage on win32

[monarch_dodra]

On Friday, 7 December 2012 at 16:23:49 UTC, Jonathan M Davis 
wrote:
> If you look in win32.mak, you'll see that the source files are 
> split into
> separate groups (STD_1_HEAVY, STD_2_HEAVY, STD_3, STD_4, etc.). 
> This is
> specifically to combat this problem. Every time that we reach 
> the point that
> the compilation starts running out of memory again, we add more 
> groups and/or
> rearrange them. It's suboptimal, but I don't know what else we 
> can do at this
> point given dmd's limitations on 32-bit Windows.
>
> - Jonathan M Davis

I had actually been through this before, and someone told me 
about that. The problem at this point is that this isn't even an 
option anymore, since std/algorithm.d is in a group *alone*.

On Friday, 7 December 2012 at 17:07:10 UTC, Nick Sabalausky wrote:
> [SNIP]
> Is this correct? If so, what's the current status of fixes? It 
> seems to
> me this would be something that should be creeping higher and 
> higher up
> the priority list (if it hasn't already been doing so).

What he said.