Plan for Exceptions and @nogc?

[Tobias Pankrath via Digitalmars-d]

> Could someone give a description of the minutiae of why 
> Exception throwing uses memory allocation as it is and why (for 
> example) passing it back on the stack isn't an option?

The stack frame of the thrower is the first one to be rolled 
back. So you cannot allocate in the stack frame of the thrower, 
but a function cannot now, who (if anyone) is catching the 
exceptions it might throw. So I fear the stack is out.