public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ensadc at mailnesia dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105351] [concepts] Constraint checking does correctly match static member attributes Date: Sat, 23 Apr 2022 13:18:22 +0000 [thread overview] Message-ID: <bug-105351-4-IXwuVMSMiQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105351-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105351 ensadc at mailnesia dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ensadc at mailnesia dot com --- Comment #3 from ensadc at mailnesia dot com --- I believe that `T::attr2` is a valid expression when it appears in a requirement. So I think GCC and Clang are correct. [expr.prim.id.general]/3: An id-expression that denotes a non-static data member or non-static member function of a class can only be used: - [...] - if that id-expression denotes a non-static data member and it appears in an unevaluated operand. [expr.prim.req.general]/2: Expressions appearing within a requirement-body are unevaluated operands.
next prev parent reply other threads:[~2022-04-23 13:18 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-22 20:29 [Bug c++/105351] New: " gawain.bolton at free dot fr 2022-04-22 20:44 ` [Bug c++/105351] " pinskia at gcc dot gnu.org 2022-04-23 7:22 ` gawain.bolton at free dot fr 2022-04-23 13:18 ` ensadc at mailnesia dot com [this message] 2022-05-01 20:02 ` gawain.bolton at free dot fr 2022-05-03 14:00 ` ppalka at gcc dot gnu.org 2022-05-03 14:24 ` ppalka at gcc dot gnu.org 2022-05-03 19:21 ` cvs-commit at gcc dot gnu.org 2023-04-18 13:38 ` ppalka 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-105351-4-IXwuVMSMiQ@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).