This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/51747] [DR 1467] [C++11] cannot call defaulted copy constructor using list-initialization
- From: "ville.voutilainen at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 16 Jan 2015 09:10:42 +0000
- Subject: [Bug c++/51747] [DR 1467] [C++11] cannot call defaulted copy constructor using list-initialization
- Auto-submitted: auto-generated
- References: <bug-51747-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51747
Ville Voutilainen <ville.voutilainen at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |ville.voutilainen at gmail dot com
Resolution|FIXED |---
--- Comment #8 from Ville Voutilainen <ville.voutilainen at gmail dot com> ---
This case fails:
struct base {
};
struct derived : base {
derived(const base &state)
: base{state} // Gcc, Clang, and EDG reject.
{}
};
void f(base b) {
derived d{b};
}
Should this be a separate bug? The call of the implicitly-defaulted
copy constructor fails using list-initialization, so this seems like
it should be part of the same PR.