On 9/23/13 8:02 AM, Adam D. Ruppe wrote:
We should really deprecate the new keyword. It'd break like all code
ever, but with D's templates, there's no need for it, and when it is
there, it is going to spark problems about replacing global allocators
or the library allocators being second class citizens.
Maybe we could minimize the breakage by just rewriting the keyword into
a library function call, which could then be overridden with local
variables or imports via normal scoping.
I'd think new already is translated into a library call. Walter?
Andrei
