http://d.puremagic.com/issues/show_bug.cgi?id=7008



--- Comment #3 from Jerry Quinn <jlqu...@optonline.net> 2011-12-11 21:32:49 PST 
---
(In reply to comment #2)
> Being an opaque pointer means that the implementation of associative arrays is
> entirely up to the runtime, not the compiler. The compiler should emit no
> dependencies on how it is implemented.

To make this work, the compiler has to have a documented interface to the AA. 
I feel we need a documented set of calls that will be output by the compiler,
just as $ is documented as being translated to length.

At the moment, the only documentation is "read this file in druntime".  It's
not a guarantee of how the compiler-AA interface works.  Without the guarantee
another compiler cannot safely generate compatible code, and debuggers can't be
guaranteed to know how to look at the contents of the AA.

Am I missing something in this request?

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------

Reply via email to