public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@acm.org>
To: Jason Merrill <jason@redhat.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: c++: template operator lookup caching
Date: Wed, 26 Aug 2020 13:14:34 -0400	[thread overview]
Message-ID: <1a8f3c70-e64f-5095-8986-2e7985ab54a9@acm.org> (raw)
In-Reply-To: <282c66f6-3d37-ae16-a814-4f069b81b4aa@redhat.com>

On 8/26/20 1:07 PM, Jason Merrill wrote:
> On 8/26/20 12:56 PM, Nathan Sidwell wrote:
>> On 8/26/20 12:06 PM, Jason Merrill wrote:
>>> On 8/26/20 8:30 AM, Nathan Sidwell wrote:
>>>>

>>>> This still retains only recording on lambdas.  As the comment says, we
>>>> could enable for all templates.
>>>
>>> If we're going to need it on all templates for modules, is there a 
>>> reason not to go ahead and make that change now?
>>
>> No reason.
>>
>>> Do we need a different approach for operator lookup in non-function 
>>> template contexts, e.g. data member initializers?
>>
>> Hm, I guess we do.
> 
> Perhaps represent the operation as a CALL_EXPR with 
> CALL_EXPR_OPERATOR_SYNTAX set?

I think that'd work.  To be strictly correct we need it everywhere, 
because (crazy user/testsuite):

template<typename T> void Foo (T t)
{
   { using namespace A;  !t; }
   { using namespace B;  !t; }
}

-- 
Nathan Sidwell

      reply	other threads:[~2020-08-26 17:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-26 12:30 Nathan Sidwell
2020-08-26 16:06 ` Jason Merrill
2020-08-26 16:56   ` Nathan Sidwell
2020-08-26 17:07     ` Jason Merrill
2020-08-26 17:14       ` Nathan Sidwell [this message]

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=1a8f3c70-e64f-5095-8986-2e7985ab54a9@acm.org \
    --to=nathan@acm.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@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).