From: Jason Merrill <jason@redhat.com>
To: Marek Polacek <polacek@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Better location info for "incomplete type" error msg (PR c/70756)
Date: Fri, 29 Apr 2016 20:04:00 -0000 [thread overview]
Message-ID: <5723BE3D.4070706@redhat.com> (raw)
In-Reply-To: <20160428155908.GQ28445@redhat.com>
On 04/28/2016 11:59 AM, Marek Polacek wrote:
> 3) for the C++ FE I used a macro so that I don't have to change all the
> cxx_incomplete_type_error calls now,
How about an inline overload, instead?
It seems sad to discard the location information; could we pass it into
cxx_incomplete_type_diagnostic?
Jason
next prev parent reply other threads:[~2016-04-29 20:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 15:59 Marek Polacek
2016-04-29 20:04 ` Jason Merrill [this message]
2016-05-02 16:41 ` Marek Polacek
2016-05-02 17:34 ` Jason Merrill
2016-05-03 11:27 ` Marek Polacek
2016-05-04 0:05 ` Jason Merrill
2016-05-04 13:00 ` Marek Polacek
2016-05-04 15:53 ` Jason Merrill
2016-05-05 14:22 ` Marek Polacek
2016-05-12 10:37 ` Marek Polacek
2016-05-12 15:09 ` 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=5723BE3D.4070706@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=polacek@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).