Decision on container design

[Andrei Alexandrescu]

On 2/2/11 8:56 AM, dsimcha wrote:
> BTW, I thought the case for a sealed hash table with an optimized memory
> allocation scheme was self-evident to most heavy D users, given how the
> builtin hash table leaks memory/fragments the heap (I think it's a
> little of both) and destroys multithreaded performance.

Perhaps a very good argument could be made with some benchmarks that 
show how your table is better than others in casual use and in heavy use.

Andrei