Blaming the D language

[Jakob Ovrum via Digitalmars-d]

On Wednesday, 22 October 2014 at 07:42:22 UTC, Jonathan M Davis 
via Digitalmars-d wrote:
> Well, the reality of the matter is that you can't truly clear 
> it safely,
> though we could definitely get closer. The in operator gives 
> pointer access to
> the internals, and the byKey and byValue may do the same (not 
> to mention,
> opApply), and they could be in progress when you try and clear 
> out the AA, so
> if you cleared it out, all of those would still have to work 
> (or maybe throw
> an Error in the cases where iteration is going on).

This is already the case because of .remove(). Adding a clear 
method wouldn't introduce any *new* problems.