From: Jason Merrill <jason@redhat.com>
To: Patrick Palka <ppalka@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 2/2] c++: remove lookup_template_class's entering_scope flag
Date: Wed, 1 May 2024 16:22:58 -0400 [thread overview]
Message-ID: <0182a4aa-cb43-42ec-b8fd-c9a23424d889@redhat.com> (raw)
In-Reply-To: <1053294c-b63c-b40b-0ba2-069e2bd615c3@idea>
On 5/1/24 12:41, Patrick Palka wrote:
> On Fri, 2 Feb 2024, Patrick Palka wrote:
>
>> Bootstrapped and regtested on x86_64-pc-linux, does this look like
>> an improvement? This is not a bugfix and barely related to the previous
>> patch, but the previous patch's new use of entering_scope=true motivated
>> me to submit this patch since it seems like a nice simplification.
>
> Ping, now that stage 1 is open.
Thanks for the ping. The earlier message isn't showing up in
Thunderbird for some reason, though I see it in the gmail web interface...
>> @@ -16771,9 +16722,10 @@ tsubst (tree t, tree args, tsubst_flags_t complain, tree in_decl)
>> ctx = TREE_VEC_ELT (ctx, 0);
>> }
>> else
>> - ctx = tsubst_aggr_type (ctx, args,
>> - complain | tf_qualifying_scope,
>> - in_decl, /*entering_scope=*/1);
>> + {
>> + ctx = tsubst_scope (ctx, args, complain, in_decl);
Why is this one tsubst_scope while the others are all plain tsubst?
Do we want a tsubst_entering_scope function?
>> + ctx = adjust_type_for_entering_scope (ctx);
next prev parent reply other threads:[~2024-05-01 20:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 19:41 [PATCH 1/2] c++: requires-exprs and partial constraint subst [PR112769] Patrick Palka
2024-02-02 19:41 ` [PATCH 2/2] c++: remove lookup_template_class's entering_scope flag Patrick Palka
2024-05-01 19:41 ` Patrick Palka
2024-05-01 20:22 ` Jason Merrill [this message]
2024-05-01 20:40 ` Patrick Palka
2024-05-01 20:52 ` Jason Merrill
2024-05-02 17:49 ` Patrick Palka
2024-05-02 18:11 ` Jason Merrill
2024-02-02 19:55 ` [PATCH 1/2] c++: requires-exprs and partial constraint subst [PR112769] Jason Merrill
2024-02-02 20:01 ` Jason Merrill
2024-02-02 20:36 ` Patrick Palka
2024-02-02 20:57 ` Patrick Palka
2024-02-02 21:05 ` Jason Merrill
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=0182a4aa-cb43-42ec-b8fd-c9a23424d889@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).