public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "daniel-dev at hotmail dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110497] Wrong error on non-static data member referenced in concept definition Date: Sun, 02 Jul 2023 08:08:51 +0000 [thread overview] Message-ID: <bug-110497-4-jC3Ct9vubn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110497-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110497 --- Comment #2 from Daniel <daniel-dev at hotmail dot de> --- Just some observations: There was a similar discussion in https://stackoverflow.com/questions/75443227/static-assert-on-an-ill-formed-no-diagnostic-required-expression Note that if we use anything else which leads to the ill-formed expression for T::b itself, e.g. B&, B*, int - gcc compiles without errors: struct B { const bool b = true; }; template <typename T> concept C = T::b; static_assert( !C<B*> ); static_assert( !C<B&> ); static_assert( !C<int> ); https://gcc.godbolt.org/z/9c6YW1vWe I would expect (at least as a user) the same behaviour for static_assert(!C<B>) too, in that case. So gcc seems to consider T::b (with T=b) in this context as a well-formed expression, but not a constant expression. Looks strange.
prev parent reply other threads:[~2023-07-02 8:08 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-30 9:23 [Bug c++/110497] New: " fchelnokov at gmail dot com 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 [this message]
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-jC3Ct9vubn@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).