public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99599] [11 Regression] Concepts requirement falsely reporting cyclic dependency, breaks tag_invoke pattern Date: Mon, 15 Mar 2021 14:20:32 +0000 [thread overview] Message-ID: <bug-99599-4-CQA67vMiwY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99599-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99599 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail| |11.0 CC| |jason at gcc dot gnu.org --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- Rejected since 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. It was pretty straightforward to insert the satisfaction check into the logic, but I needed to make the 3-parameter version of satisfy_declaration_constraints call push_tinst_level like the 2-parameter version already does. For simplicity, I also made it add any needed outer template arguments from the TEMPLATE_DECL to the args. The testsuite changes are mostly because this change causes unsatisfaction to cause deduction to fail rather than reject the candidate later in overload resolution.
next prev parent reply other threads:[~2021-03-15 14:20 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-15 13:24 [Bug c++/99599] New: Concepts requirement falsely reporting recursion, " the_gamester28 at msn dot com 2021-03-15 13:49 ` [Bug c++/99599] [11 Regression] Concepts requirement falsely reporting cyclic dependency, " rguenth at gcc dot gnu.org 2021-03-15 14:20 ` redi at gcc dot gnu.org [this message] 2021-04-01 22:04 ` jason at gcc dot gnu.org 2021-04-02 12:47 ` gcc-bugs at marehr dot dialup.fu-berlin.de 2021-04-05 19:49 ` the_gamester28 at msn dot com 2021-04-27 11:40 ` [Bug c++/99599] [11/12 " jakub at gcc dot gnu.org 2021-05-01 17:38 ` ppalka at gcc dot gnu.org 2021-07-28 7:06 ` rguenth at gcc dot gnu.org 2021-08-25 14:44 ` ppalka at gcc dot gnu.org 2022-04-21 7:48 ` rguenth at gcc dot gnu.org 2022-08-08 15:06 ` [Bug c++/99599] [11/12/13 " ppalka at gcc dot gnu.org 2022-10-27 12:42 ` ppalka at gcc dot gnu.org 2023-04-04 5:33 ` catsith at me dot com 2023-05-29 10:04 ` [Bug c++/99599] [11/12/13/14 " jakub at gcc dot gnu.org 2023-06-07 18:25 ` danakj at orodu dot net 2023-06-07 18:41 ` danakj at orodu dot net 2023-06-07 20:03 ` danakj at orodu dot net 2023-08-01 18:16 ` ppalka at gcc dot gnu.org 2023-09-08 16:03 ` cvs-commit at gcc dot gnu.org 2024-02-02 18:02 ` [Bug c++/99599] [11/12/13 " ppalka at gcc dot gnu.org 2024-03-09 15:37 ` ppalka at gcc dot gnu.org 2024-03-21 21:40 ` redi at gcc dot gnu.org 2024-03-21 21:43 ` redi at gcc dot gnu.org 2024-03-22 14:08 ` ppalka at gcc dot gnu.org 2024-03-22 15:58 ` redi at gcc dot gnu.org 2024-03-27 23:16 ` redi at gcc dot gnu.org 2024-03-27 23:18 ` redi 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-99599-4-CQA67vMiwY@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).