[Bug libstdc++/61023] set/map move assignment doesn't move (or copy) the comparator

2014-05-06 Thread ppluzhnikov at google dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61023 Paul Pluzhnikov ppluzhnikov at google dot com changed: What|Removed |Added CC|

[Bug libstdc++/61023] set/map move assignment doesn't move (or copy) the comparator

2014-05-04 Thread redi at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61023 Jonathan Wakely redi at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last

[Bug libstdc++/61023] set/map move assignment doesn't move (or copy) the comparator

2014-05-01 Thread nevin at eviloverlord dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61023 --- Comment #4 from Nevin Liber nevin at eviloverlord dot com --- Good point about the Standard. However, the current behavior for move assignment breaks the invariant of the container, since the comparator is what enforces the insertion ordering

[Bug libstdc++/61023] set/map move assignment doesn't move (or copy) the comparator

2014-04-30 Thread nevin at eviloverlord dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61023 --- Comment #1 from Nevin Liber nevin at eviloverlord dot com --- Created attachment 32719 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=32719action=edit Test case using set showing the problem

[Bug libstdc++/61023] set/map move assignment doesn't move (or copy) the comparator

2014-04-30 Thread nevin at eviloverlord dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61023 --- Comment #2 from Nevin Liber nevin at eviloverlord dot com --- Also happens with multiset and multimap.

[Bug libstdc++/61023] set/map move assignment doesn't move (or copy) the comparator

2014-04-30 Thread redi at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61023 --- Comment #3 from Jonathan Wakely redi at gcc dot gnu.org --- The standard forgot to say what should happen: http://cplusplus.github.io/LWG/lwg-active.html#2227