This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/59872] New: Cannot move std::map with move-only mapped_type
- From: "potswa at mac dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 18 Jan 2014 11:17:16 +0000
- Subject: [Bug libstdc++/59872] New: Cannot move std::map with move-only mapped_type
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59872
Bug ID: 59872
Summary: Cannot move std::map with move-only mapped_type
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: potswa at mac dot com
This fails because the std::map move constructor apparently invokes a copy
operation. It was working recently (on trunk), so it looks like a regression.
#include <map>
#include <memory>
std::map< int, std::unique_ptr< int > > q, r( std::move( q ) );