From: Dodji Seketeli <dodji@redhat.com>
To: Jason Merrill <jason@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR c++/50852 - loose template parameter comparison
Date: Thu, 26 Jan 2012 22:16:00 -0000 [thread overview]
Message-ID: <m3d3a6m7oh.fsf@redhat.com> (raw)
In-Reply-To: <4F21C8D1.5070205@redhat.com> (Jason Merrill's message of "Thu, 26 Jan 2012 16:42:41 -0500")
Jason Merrill <jason@redhat.com> writes:
> Hmm...what if rather than trying to ignore levels when comparing, we
> make it so the sibling list always has level 1?
I am not sure to understand how you'd do that. You mean that instead of
pointing to the actual vector of innermost template parms,
TEMPLATE_PARM_SIBLINGS would instead point to a vector that is a copy of
the innermost template parms into which we'd have substituted and index
of level 1 for the index of each parm?
> BTW, let's avoid calling a function named *_real directly from client
> code.
Ah, oops sorry. I thought it would be OK as cp-tree.h already has a few
spots of public entry points "overloaded" using that _real suffix. What
suffix would be best?
--
Dodji
next prev parent reply other threads:[~2012-01-26 22:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 21:56 Dodji Seketeli
2012-01-17 19:03 ` Jason Merrill
2012-01-24 9:45 ` Dodji Seketeli
2012-01-26 21:43 ` Jason Merrill
2012-01-26 22:16 ` Dodji Seketeli [this message]
2012-01-26 22:52 ` Jason Merrill
2012-03-08 13:22 ` [PATCH] PR c++/50852 - Revisit dependant template parameter Dodji Seketeli
2012-03-08 20:17 ` Jason Merrill
2012-03-09 10:04 ` Dodji Seketeli
2012-03-13 21:33 ` Jason Merrill
2012-03-25 18:12 ` Dodji Seketeli
2012-03-27 17:30 ` Dodji Seketeli
2012-03-28 15:02 ` Dodji Seketeli
2012-03-28 15:26 ` Jason Merrill
2012-03-28 17:10 ` Dodji Seketeli
2012-03-28 20:38 ` Jason Merrill
2012-04-12 21:08 ` [PATCH] PR c++/50852 - loose template parameter comparison Jason Merrill
2012-07-05 18:11 ` 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=m3d3a6m7oh.fsf@redhat.com \
--to=dodji@redhat.com \
--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).