public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53903] New: [C++11] Incompatible exception-specification allowed if member explicitly-defaulted after first declaration Date: Mon, 09 Jul 2012 16:14:00 -0000 [thread overview] Message-ID: <bug-53903-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53903 Bug #: 53903 Summary: [C++11] Incompatible exception-specification allowed if member explicitly-defaulted after first declaration Classification: Unclassified Product: gcc Version: 4.7.1 Status: UNCONFIRMED Keywords: accepts-invalid Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: redi@gcc.gnu.org CC: jason@gcc.gnu.org struct T { T() noexcept(false) { } ~T() noexcept(false) { } }; struct A { A() noexcept; ~A() noexcept; T t; }; A::A() noexcept = default; A::~A() noexcept = default; This is accepted, but I think it shouldn't be. [dcl.fct.def.default]/2 An explicitly-defaulted function [...] may have an explicit exception-specification only if it is compatible (15.4) with the exception specification on the implicit declaration." The implicit declarations for A::A() and A::~A() would be noexcept(false) which is not compatible. If the functions are defaulted on their first declaration they get rejected: struct T { T() noexcept(false) { } ~T() noexcept(false) { } }; struct A { A() noexcept = default; ~A() noexcept = default; T t; }; ex.cc:8:5: error: function 'A::A()' defaulted on its first declaration with an exception-specification that differs from the implicit declaration 'A::A()' A() noexcept = default; ^ ex.cc:9:5: error: function 'A::~A()' defaulted on its first declaration with an exception-specification that differs from the implicit declaration 'A::~A()' ~A() noexcept = default; ^ The diagnostic specifically refers to defaulted on first declaration, implying that's significant, but the [dcl.fct.def.default] wording above doesn't distinguish between explicitly defaulting on the first declaration or after it.
reply other threads:[~2012-07-09 16:14 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-53903-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).