http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48848
--- Comment #12 from Paolo Carlini <paolo.carlini at oracle dot com> 2011-05-03 10:11:48 UTC --- I think I see what you mean, but actually, I'm not sure that this kind of sophistication would be consistent with the rationale of LWG 675: if I understand it correctly, we really want the move-assigned-to object to behave similarly to the copy-assigned-to object, thus destruct and release immediately, no? We want the moral equivalent of this->clear() & this->swap(__other).
