[Issue 1654] Array concatenation should result in mutable or invariant depending on usage

[d-bugmail at puremagic.com]

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





------- Comment #3 from andrei at metalanguage.com  2008-01-31 15:45 -------
The rule you mention was suggested and rejected. It is sound, but the problem
with it is that the semantics of a type becomes implicitly dependent on an
implementation detail (e.g. a private pointer member). We don't want to
separate "types with at least a pointer in'em" from "types with no pointers
in'em". 


--