public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/102529] ctad for aliases fails in the presence of constraints Date: Thu, 09 Mar 2023 15:28:03 +0000 [thread overview] Message-ID: <bug-102529-4-Uuemkje6bi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102529-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102529 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:afe1f0c251d0429069c2414d4f3f14042efc174f commit r13-6556-gafe1f0c251d0429069c2414d4f3f14042efc174f Author: Jason Merrill <jason@redhat.com> Date: Thu Feb 9 12:58:35 2023 -0800 c++: CTAD for less-specialized alias template [PR102529] The standard was unclear what happens with the transformation of a deduction guide if the initial template argument deduction fails for a reason other than not deducing all the arguments; my implementation assumed that the right thing was to give up on the deduction guide. But in consideration of CWG2664 this week I realized that we get a better result by just continuing with an empty set of deductions, so the alias deduction guide is the same as the original deduction guide plus the deducible constraint. DR 2664 PR c++/102529 gcc/cp/ChangeLog: * pt.cc (alias_ctad_tweaks): Continue after deduction failure. gcc/testsuite/ChangeLog: * g++.dg/DRs/dr2664.C: New test. * g++.dg/cpp2a/class-deduction-alias15.C: New test.
next prev parent reply other threads:[~2023-03-09 15:28 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-29 15:11 [Bug c++/102529] New: " barry.revzin at gmail dot com 2021-09-29 15:24 ` [Bug c++/102529] " ppalka at gcc dot gnu.org 2022-06-02 19:22 ` ppalka at gcc dot gnu.org 2022-06-09 13:31 ` ppalka at gcc dot gnu.org 2023-02-09 22:04 ` jason at gcc dot gnu.org 2023-03-09 15:28 ` cvs-commit at gcc dot gnu.org [this message] 2023-03-09 15:29 ` jason 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-102529-4-Uuemkje6bi@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).