"Jonathan M Davis" wrote in message
news:xjmfhegvanqdivhbt...@forum.dlang.org...
AFAIK, the only reason that it's not deprecated is that no one has
bothered to make the change (and you didn't want to deprecate it when you
went through all of those and updated their status a while back). Andrei
has stated on multiple occasions that it's going, and I think that Walter
has said the same. Arguably, it should have been deprecated ages ago. The
only good argument I see for keeping it around is that we don't have the
custom allocators yet, so it's royal pain for anyone to construct classes
on the malloc heap instead of on the GC heap (since using emplace to do it
is non-trivial), and anyone who's using delete and really doesn't want to
wait for the GC to collect the memory doesn't have an easy alternative at
the moment.
Until it actually gets merged in, nothing is certain. delete is not
particularly dangerous now that we have @safe working, and it might be nice
to have on non-GC platforms. Anyway, that's a discussion for when somebody
actually tries to get rid of it.
