From: Jason Merrill <jason@redhat.com>
To: gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: C++ PATCH for c++/48557 (SFINAE failure with void operands)
Date: Thu, 14 Apr 2011 14:58:00 -0000 [thread overview]
Message-ID: <4DA70B92.4090909@redhat.com> (raw)
In-Reply-To: <4DA70B4F.2000705@redhat.com>
On 04/14/2011 10:57 AM, Jason Merrill wrote:
> We were just failing to check complain for this one error.
Er, actually that's the next patch. For this one, we were complaining
in decay_conversion about misuse of void. I noticed that some other
places avoid calling that on void operands, so that's what I did here as
well.
Jason
prev parent reply other threads:[~2011-04-14 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 14:57 Jason Merrill
2011-04-14 14:58 ` Jason Merrill [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=4DA70B92.4090909@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
/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).