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++/96840] [11 Regression] Recursive substitution in constrained commutative operator
Date: Mon, 28 Sep 2020 15:33:03 +0000 [thread overview]
Message-ID: <bug-96840-4-koaGI00L9W@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96840-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96840
Patrick Palka <ppalka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at gcc dot gnu.org,
| |ppalka at gcc dot gnu.org
--- Comment #1 from Patrick Palka <ppalka at gcc dot gnu.org> ---
Started with r11-2774:
c++: Check satisfaction before non-dep convs. [CWG2369]
It's very hard to use concepts to protect a template from hard errors due
to
unwanted instantiation if constraints aren't checked until after doing all
substitution and checking of non-dependent conversions.
We fall into a loop when checking the constraints of the second overload
(instantiated with Rep=int and T=Int<int>).
It looks like we're correct to reject the testcase as of this DR?
next prev parent reply other threads:[~2020-09-28 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 0:29 [Bug c++/96840] New: " johelegp at gmail dot com
2020-08-31 6:31 ` [Bug c++/96840] [11 Regression] " rguenth at gcc dot gnu.org
2020-09-28 15:33 ` ppalka at gcc dot gnu.org [this message]
2020-10-16 12:05 ` rguenth at gcc dot gnu.org
2020-12-18 3:36 ` cvs-commit at gcc dot gnu.org
2021-02-01 17:58 ` ppalka at gcc dot gnu.org
2021-12-30 14:06 ` johelegp at gmail dot com
2021-12-30 14:23 ` johelegp at gmail dot com
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-96840-4-koaGI00L9W@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).