OSNews article about C++09 degenerates into C++ vs. D discussion

[Unknown W. Brackets]

But those things *are* in Phobos.

One could, for example, throw an exception or generate an assert when 
they are used, at the very least, were they to be disallowed.

Or, those things could be garbage collected, and manual runs could be 
scheduled for any such.  in any case, the rest of the library could have 
no gc usage.

It's really any time you get something for nothing, after all.  It's not 
really that difficult to tell what uses memory, whether it has "new" in 
it or not - imho.

-[Unknown]


> It's not just a library issue, and in some ways I think it *would* be
> significantly more painful than in C++. D has a lot of innocuous-looking syntax
> that allocates heap memory non-obviously; AA and dynamic array initialization
> syntax, for instance. Without a GC, that's a lot of leaks and/or runtime errors
> waiting to happen.