On Sunday, 2 April 2017 at 05:16:23 UTC, Walter Bright wrote:
then it is optimized to call 'allocate' instead.

Sounds like using compiler magic for changing the behavior of existing syntax rather than fixing the actual problem that std.allocators is trying to solve: unifying disparate allocation strategies/needs across libraries.

Do we really want to break a bunch of code and add another special case for this one specific problem, thereby making an already complicated language even more complicated?

Also, half of the nogc purists aren't going to be using druntime anyway.

Reply via email to