From: Tom Tromey <tromey@redhat.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: Project Archer <archer@sourceware.org>
Subject: Re: Question on pr python/11060
Date: Fri, 15 Jan 2010 17:04:00 -0000 [thread overview]
Message-ID: <m36373e1v2.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4B50992F.3080908@redhat.com> (Phil Muldoon's message of "Fri, 15 Jan 2010 16:34:55 +0000")
>>>>> "Phil" == Phil Muldoon <pmuldoon@redhat.com> writes:
Phil> http://sourceware.org/bugzilla/show_bug.cgi?id=11060
Phil> I believe this is happening as DEMANGLE_COMPONENT_LITERAL is not
Phil> being accounted for in the type lookup. In this case of a template
Phil> argument resolving to LITERAL, is it ok just to return the type
Phil> backing the argument without further manipulation?
I think that in the literal case, Type.template_argument should return
the literal -- not the type of the literal.
This means you would have to turn the literal into a Value with the
proper type.
Tom
prev parent reply other threads:[~2010-01-15 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 16:35 Phil Muldoon
2010-01-15 17:04 ` Tom Tromey [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=m36373e1v2.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=archer@sourceware.org \
--cc=pmuldoon@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).