This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/46736] [c++0x] move constructor is not implicitly deleted when it should be
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 1 Dec 2010 09:27:45 +0000
- Subject: [Bug c++/46736] [c++0x] move constructor is not implicitly deleted when it should be
- Auto-submitted: auto-generated
- References: <bug-46736-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46736
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at gcc dot gnu.org
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> 2010-12-01 09:27:42 UTC ---
Jason, could you take a look?
Shouldn't a user-provided move constructor still be defined as deleted if
there's a subobject that isn't trivially copyable?