http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48848
--- Comment #8 from Paolo Carlini <paolo.carlini at oracle dot com> 2011-05-03 00:52:11 UTC --- And I think that in the FDIS we have a defect for the move assignment operator: it is supposed to be both noexcept and constant complexity and I don't see how those can be achieved given the "as if by calling resize(v.size())" semantics. Then, even assuming we "ignore" the "as if", as some sort of pasto, and proceed with plain swaps of the data members, we are still not completely happy, because, from at least the QoI point of view, we would like to ensure for valarray too the resolution of LWG 675 for containers, thus we want to destroy first all the existing elements, the complexity is again in principle non-constant. Jon, do you have an opinion about this? I'm thinking of just swapping for now, but also raise the issue on the reflector.
