public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/102012] GCC accepts any non-bool atomic constraint type
Date: Tue, 24 Aug 2021 17:28:52 +0000	[thread overview]
Message-ID: <bug-102012-4-i1fC80HDds@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102012-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102012

--- Comment #4 from Patrick Palka <ppalka at gcc dot gnu.org> ---
(In reply to 康桓瑋 from comment #3)
> (In reply to Patrick Palka from comment #1)
> > Hmm, I think this might actually be well-formed according to [temp.names]/9.
> > I don't see why we'd need to check satisfaction of a concept-id inside
> > decltype if its type is already prescribed to be bool.
> 
> "The standard requires MSVC/Clang's behavior of erroring out." from
> https://stackoverflow.com/a/68910627/11638718.

Yes, evaluation of the concept-id should produce an error during satisfaction
due to the non-bool constraint.  But why should we evaluate a concept-id inside
decltype in the first place, when the type of a concept-id is always prescribed
to be bool?

      parent reply	other threads:[~2021-08-24 17:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-22 15:14 [Bug c++/102012] New: " hewillk at gmail dot com
2021-08-23 10:05 ` [Bug c++/102012] " redi at gcc dot gnu.org
2021-08-23 14:28 ` ppalka at gcc dot gnu.org
2021-08-23 14:39 ` hewillk at gmail dot com
2021-08-24 16:56 ` hewillk at gmail dot com
2021-08-24 17:28 ` ppalka at gcc dot gnu.org [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-102012-4-i1fC80HDds@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).