On 11 June 2010 18:50, David Simcha <[email protected]> wrote: > Ok, I see why. I had 2.046 and the beta installed concurrently, and I > forgot to point my path variable at the beta before building Phobos. Now I > can reproduce this, both using the Phobos build scripts and compiling the > file individually with unittests turned on from Codeblocks. It still works > fine on 2.046, though I did notice that DMD does take a while to > (successfully) compile it and uses ~60 MB of memory. It looks like a > compiler regression, or else CustomFloat was relying on a bug that got > fixed.
It seems to be a recursive mixin. Every time it's instantiated, it gets 4 bytes bigger. Seems to be triggered by opOpAssign; maybe it's the change to opOpAssign in this release: "+=" was passed to opOpAssign now it's "+". There's code in opOpAssign which is clearly wrong - it's stripping off the "=", which no longer exists. If you don't think you can fix this really quickly, I think we should remove it completely from this release, and wait until the next one. It doesn't seem urgent to me, but getting a release out is urgent. _______________________________________________ phobos mailing list [email protected] http://lists.puremagic.com/mailman/listinfo/phobos
