public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "de34 at live dot cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107256] New: Contradictory circular noexcept-specifier is accepted
Date: Fri, 14 Oct 2022 02:06:58 +0000 [thread overview]
Message-ID: <bug-107256-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107256
Bug ID: 107256
Summary: Contradictory circular noexcept-specifier is accepted
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Keywords: accepts-invalid
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: de34 at live dot cn
Target Milestone: ---
This code snipet is currently accepted by gcc while the noexcept-specifier
cannot be meaningful.
struct Weird {
static void f() noexcept(!noexcept(Weird::f())) {}
};
Godbolt link: https://godbolt.org/z/hqnha3aPd
The code was rejected by gcc 9 and earlier versions, but with a seemly
incorrect reason (error: incomplete type 'Weird' used in nested name
specifier). According to CWG DR 1330 and current wording in [class.mem.general]
/7, the noexcept-specifier establishes a complete-class context, so Weird is
complete inside it.
next reply other threads:[~2022-10-14 2:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 2:06 de34 at live dot cn [this message]
2022-10-14 9:06 ` [Bug c++/107256] " redi at gcc dot gnu.org
2022-10-18 19:33 ` mpolacek at gcc dot gnu.org
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-107256-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: link
Be 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).