[Issue 2632] Setting length on invalid arrays causes assertion failure with a debug runtime

[d-bugmail at puremagic.com]

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


matti.niemenmaa+dbugzilla at iki.fi changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Phobos                      |www.digitalmars.com
           Keywords|                            |spec




------- Comment #1 from matti.niemenmaa+dbugzilla at iki.fi  2009-02-08 10:33 -------
I'm moving this to www.digitalmars.com and adding the 'spec' keyword since it
seems that there's absolutely nothing written down about this possibility. I
believe this needs to be clarified. If the answer indicates that Phobos should
change, I'll file a separate bug for that.

The basic issue is, what operations, if any, are allowed on dynamic arrays
which are in an invalid state, i.e. have a nonzero length but a null pointer?
(I suppose the converse—nonnull pointer but zero length—is fine.)
"Implementation defined" is a fine answer as long as it's actually specified.

Associative arrays don't have this problem since their ABI says that they're
just a pointer to an implementation defined type.


--