Peter Alexander <> changed:

           What    |Removed                     |Added
                 CC|                            |
                   |                            |m

--- Comment #3 from Peter Alexander <> 2010-10-27 
12:02:23 PDT ---
(In reply to comment #2)
> Regardless, I don't see why it would matter what the state of the object is
> prior to opAssign() being called. That's like caring whether the invariant is
> true prior to the constructor call.

It matters if the object being assigned to have resources that it needs to free
(with the invariant possibly being that a pointer to the resource is non-null).

I agree 100% with Don here: .init should satisfy the invariant, which makes
this bug into a non-bug (unless you can think of other valid situations where
the invariant is broken prior to an opAssign call?)

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to