public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "richard-gccbugzilla at metafoo dot co.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109337] c++2a test concepts4.C passes when it should fail
Date: Wed, 29 Mar 2023 20:13:23 +0000 [thread overview]
Message-ID: <bug-109337-4-KoQbd4Cpcy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109337-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109337
Richard Smith <richard-gccbugzilla at metafoo dot co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |richard-gccbugzilla@metafoo
| |.co.uk
--- Comment #6 from Richard Smith <richard-gccbugzilla at metafoo dot co.uk> ---
(In reply to Andrew Pinski from comment #5)
> (In reply to Christopher Di Bella from comment #3)
> > This is apparently a Clang bug: the RHS of `R42c` isn't evaluated because of
> > short-circuiting. Apologies for the noise and thanks for helping me work
> > through it.
>
> No, clang and GCC disagree even on:
> ```
> template <class Ub> concept A42b = true;
> template <class Tc> concept R42c = A42b<Tc&>;
>
> static_assert (R42c<void>);
> ```
>
> There is no short-circuting here.
No substitution is performed into 'Tc&' here, because normalization of R42c
produces the atomic constraint 'true' with an empty parameter mapping. So the
type 'void&' is never formed.
next prev parent reply other threads:[~2023-03-29 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 18:55 [Bug c++/109337] New: " cjdb.ns at gmail dot com
2023-03-29 18:59 ` [Bug c++/109337] " pinskia at gcc dot gnu.org
2023-03-29 19:02 ` pinskia at gcc dot gnu.org
2023-03-29 19:08 ` cjdb.ns at gmail dot com
2023-03-29 19:09 ` pinskia at gcc dot gnu.org
2023-03-29 19:11 ` pinskia at gcc dot gnu.org
2023-03-29 20:13 ` richard-gccbugzilla at metafoo dot co.uk [this message]
2023-03-30 17:08 ` 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-109337-4-KoQbd4Cpcy@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).