From: Jason Merrill <jason@redhat.com>
To: Patrick Palka <ppalka@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] c++/modules: member alias tmpl partial inst [PR103994]
Date: Wed, 6 Mar 2024 22:55:58 -0500 [thread overview]
Message-ID: <61fbdfa3-e7ad-48bc-ba06-42ae41cfcf4f@redhat.com> (raw)
In-Reply-To: <20240304222654.1511204-1-ppalka@redhat.com>
On 3/4/24 17:26, Patrick Palka wrote:
> Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look
> OK for trunk?
>
> -- >8 --
>
> Alias templates are weird in that their specializations can appear in
> both decl_specializations and type_specializations. They appear in the
> latter only at parse time via finish_template_type. This should probably
> be revisited in GCC 15 since it seems sufficient to store them only in
> decl_specializations.
It looks like most all of lookup_template_class is wrong for alias
templates.
Can we move the alias template handling up higher and unconditionally
return the result of tsubst?
Jason
next prev parent reply other threads:[~2024-03-07 3:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 22:26 Patrick Palka
2024-03-07 3:55 ` Jason Merrill [this message]
2024-03-07 16:06 ` Patrick Palka
2024-03-07 19:41 ` Patrick Palka
2024-03-07 20:43 ` Jason Merrill
2024-03-07 20:58 ` Patrick Palka
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=61fbdfa3-e7ad-48bc-ba06-42ae41cfcf4f@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ppalka@redhat.com \
/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).