public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fchelnokov at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/110497] New: Wrong error on non-static data member referenced in concept definition
Date: Fri, 30 Jun 2023 09:23:52 +0000 [thread overview]
Message-ID: <bug-110497-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110497
Bug ID: 110497
Summary: Wrong error on non-static data member referenced in
concept definition
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: fchelnokov at gmail dot com
Target Milestone: ---
This program
struct B {
const bool b = true;
};
template <typename T>
concept C = T::b;
static_assert( !C<B> );
is accepted in Clang. And I think correctly accepted because of substitution
failure per https://eel.is/c++draft/temp.constr.constr#temp.constr.op-5
> [...] Furthermore, if substitution to determine whether an atomic constraint is satisfied ([temp.constr.atomic]) encounters a substitution failure, the constraint is not satisfied, regardless of the presence of a negation operator.
But GCC emits a weird error (at least the error text must be adjusted):
error: '*(B*)(void)0' is not a constant expression
Online demo: https://gcc.godbolt.org/z/xKf13cb6v
next reply other threads:[~2023-06-30 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 9:23 fchelnokov at gmail dot com [this message]
2023-06-30 9:41 ` [Bug c++/110497] " redi at gcc dot gnu.org
2023-06-30 13:44 ` ppalka at gcc dot gnu.org
2023-07-02 8:08 ` daniel-dev at hotmail dot de
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-110497-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).