This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/51747] New: [C++11] cannot call copy constructor using list-initialization
- 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: Tue, 03 Jan 2012 22:04:09 +0000
- Subject: [Bug c++/51747] New: [C++11] cannot call copy constructor using list-initialization
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51747
Bug #: 51747
Summary: [C++11] cannot call copy constructor using
list-initialization
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: redi@gcc.gnu.org
CC: jason@gcc.gnu.org
struct X {
X() = default;
X(const X&) = default;
#ifdef OK
X(int) { }
#endif
};
X x;
X x2{x};
t.cc:10:7: error: too many initializers for 'X'
(It compiles fine if OK is defined.)
Should overload resolution choose the copy constructor?
If not, could there be a better diagnostic?