This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/55924] [C++11] Not all copy-assignment operator forms are correctly detected
- 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, 09 Jan 2013 18:39:46 +0000
- Subject: [Bug c++/55924] [C++11] Not all copy-assignment operator forms are correctly detected
- Auto-submitted: auto-generated
- References: <bug-55924-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55924
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2013-01-09
Ever Confirmed|0 |1
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> 2013-01-09 18:39:46 UTC ---
Clang thinks you need to add
mine() = default;
mine(const mine&) = default;
for the code to be accepted and I agree, otherwise the operator=(mine)
assignment operator calls the copy constructor which is deleted because of a
user-declared move assignment operator.