On Wednesday, 9 October 2013 at 04:24:23 UTC, Jonathan M Davis
wrote:
Except that for the most part, that's the only way that
immutable objects can
be created - particularly if you're talking about arrays or
AAs. It's _very_
common to do what Walter is describing. On top of that, we're
forced to cast
to immutable or shared to pass anything via std.concurrency,
which causes
pretty much the same problem. We're not even vaguely set up at
this point to
have type qualifiers indicate how something was constructed or
what thread it
comes from.
As said, we can update the runtime interface while having
everything allocated in the same pool.
