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++/105841] [12/13 Regression] Change in behavior of CTAD for alias templates
Date: Thu, 09 Mar 2023 15:27:57 +0000	[thread overview]
Message-ID: <bug-105841-4-aqE3SkOcgT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105841-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 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:9e6170098d5e7756e85e880f8f4cb18e885a64fd

commit r13-6555-g9e6170098d5e7756e85e880f8f4cb18e885a64fd
Author: Jason Merrill <jason@redhat.com>
Date:   Wed Feb 8 22:06:22 2023 -0800

    c++: fix alias CTAD [PR105841]

    In my initial implementation of alias CTAD, I described a couple of
    differences from the specification that I thought would not have a
practical
    effect; this testcase demonstrates that I was wrong.  One difference is
    resolved by the CPTK_IS_DEDUCIBLE commit; the other (adding too many of the
    alias template parameters to the new deduction guide) is fixed by this
    patch.

            PR c++/105841

    gcc/cp/ChangeLog:

            * pt.cc (corresponding_template_parameter_list): Split out...
            (corresponding_template_parameter): ...from here.
            (find_template_parameters): Factor out...
            (find_template_parameter_info::find_in): ...this function.
            (find_template_parameter_info::find_in_recursive): New.
            (find_template_parameter_info::found): New.
            (alias_ctad_tweaks): Only add parms used in the deduced args.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp2a/class-deduction-alias14.C: New test.

    Co-authored-by: Michael Spertus <mike@spertus.com>

  parent reply	other threads:[~2023-03-09 15:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03 18:12 [Bug c++/105841] New: " avemilia at protonmail dot com
2022-06-06 12:50 ` [Bug c++/105841] [12/13 Regression] " ppalka at gcc dot gnu.org
2022-06-06 19:28 ` jason at gcc dot gnu.org
2022-06-06 20:12 ` jason at gcc dot gnu.org
2022-06-07  0:02 ` mike at spertus dot com
2022-06-07  4:05 ` jason at gcc dot gnu.org
2022-06-09 13:39 ` ppalka at gcc dot gnu.org
2022-07-25 16:11 ` rguenth at gcc dot gnu.org
2023-02-09 22:05 ` jason at gcc dot gnu.org
2023-02-09 23:07 ` jason at gcc dot gnu.org
2023-02-09 23:26 ` mike at spertus dot com
2023-02-10 16:29 ` mike at spertus dot com
2023-03-09 15:27 ` cvs-commit at gcc dot gnu.org
2023-03-09 15:27 ` cvs-commit at gcc dot gnu.org [this message]
2023-03-09 15:30 ` [Bug c++/105841] [12 " jason at gcc dot gnu.org
2023-05-08 12:24 ` rguenth at gcc dot gnu.org
2023-12-20 22:23 ` jason at gcc dot gnu.org
2024-04-17 12:22 ` hokein.wu at gmail dot com
2024-04-24 21:41 ` ppalka at gcc dot gnu.org
2024-04-25 10:31 ` hokein.wu 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-105841-4-aqE3SkOcgT@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).