https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61143
--- Comment #13 from François Dumont fdumont at gcc dot gnu.org ---
Author: fdumont
Date: Fri May 23 19:35:12 2014
New Revision: 210876
URL: http://gcc.gnu.org/viewcvs?rev=210876root=gccview=rev
Log:
2014-05-23 François Dumont
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61143
François Dumont fdumont at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61143
--- Comment #12 from François Dumont fdumont at gcc dot gnu.org ---
Author: fdumont
Date: Wed May 21 19:51:05 2014
New Revision: 210726
URL: http://gcc.gnu.org/viewcvs?rev=210726root=gccview=rev
Log:
2014-05-21 François Dumont
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61143
Jonathan Wakely redi at gcc dot gnu.org changed:
What|Removed |Added
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61143
Jonathan Wakely redi at gcc dot gnu.org changed:
What|Removed |Added
Severity|normal |major
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61143
--- Comment #9 from Felix Fontein felix at fontein dot de ---
Another workaround is to use reserve(), as in:
std::unordered_mapint, int b = std::move(a);
a.reserve(1); // any number 0 will do
a.emplace(1, 1);
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61143
François Dumont fdumont at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61143
Jonathan Wakely redi at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61143
--- Comment #5 from Jonathan Wakely redi at gcc dot gnu.org ---
(In reply to François Dumont from comment #4)
I simply considered that the moved container instance wouldn't be reused
this way, just potentially for some immutable operations. I
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61143
--- Comment #6 from Marc Glisse glisse at gcc dot gnu.org ---
There was that whole discussion on how much sense it makes to make move
constructors noexcept when default constructors aren't...
10 matches
Mail list logo