core.exception.InvalidMemoryOperationError@(0)

[ketmar via Digitalmars-d-learn]

On Mon, 26 Jan 2015 11:37:12 +0000, Bayan Rafeh wrote:

>> you are trying to use invariants for the things that invariants can't
>> (and must not) check. invariants are meant for checking *internal*
>> *object* *consistency*. NOT correctness. NOT applicability. ONLY
>> consistency. object can be in "inapplicable" state, but still
>> consistent.
> 
> Then I must have misunderstood the documentation, I apologize, I thought
> the point of invariant was to ensure correctness of the object's state.
> I'll go ahead and report the bug.

but please, take my words with a grain of salt. i'm in no way a 
representative of D devs. that is how *i* understand invariants. it seems 
to be consistent with the cases where invariant works, but the designers 
may have different opinion, and don't have time to properly fix invariant 
handling.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.puremagic.com/pipermail/digitalmars-d-learn/attachments/20150126/dbfe3be3/attachment.sig>