Escape analysis

[Steven Schveighoffer]

"Bill Baxter" wrote
> Back to the technical topic, as I told Andrei, all I want is some
> solution that doesn't kill performance with lots of hidden memory
> allocations.
> I doubt that's something anyone really wants, so all this huffing and
> puffing about it probably isn't necessary.

I doubt anyone wants that.  But here is my main concern (my defense for 
huffing):

One of my main goals for D at the moment is to have Tango compile on D2. 
Right now, I'm slowly getting everything constified, and dealing with small 
design changes to make that happen (and filing bugs that I find).

However, when dissecting solutions to unnecessary dynamic closures, I want 
to make sure that the solution does not force Tango to change its overall 
design.  Right now, with Walter's proposal, I fear a large amount of scope 
decorations would be necessary (making the api very unattractive), and 
possibly some of the ways Tango uses stack variables might be made 
uncompilable.  I would like to avoid that.  It has happened in the past that 
things considered closed on D2 did not work with Tango because the main code 
used to test D2 (Phobos) does not have a similar design, and does not use 
the same features as Tango does.

When I think a solution solves the problem, and will allow Tango to compile, 
I'll stop my whining ;)

-Steve