LinkedIn Article to be: Why you need to start moving off C/C++ to D, now.

[deadalnix via Digitalmars-d]

On Thursday, 17 July 2014 at 19:19:40 UTC, Tobias Müller wrote:
> 1. "There is no deallocation" is just plain wrong.
>

It is actually fairly common to not deallocate and reuse the pool 
for later allocations.

Also, it doesn't matter as the complexity of deallocation doesn't 
depend on the size of the block deallocated.

In the case of a copying collector, the deallocation won't even 
show up in benchmark as tracing and copying will dominate CPU 
time by a LOT !