From: Jason Merrill <jason@redhat.com>
To: Paolo Carlini <paolo.carlini@oracle.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ Patches] PR c++/66781 and c++/67847
Date: Wed, 21 Oct 2015 19:24:00 -0000 [thread overview]
Message-ID: <5627E555.50405@redhat.com> (raw)
In-Reply-To: <5627A31B.90402@oracle.com>
On 10/21/2015 04:37 AM, Paolo Carlini wrote:
> + "%qD is not an enumerator-name", identifier);
This should be enum-name or "does not name an enumeration". We should
also print the nested-name-specifier.
> + error_at (type_start_token->location, "nested name specifier "
> + "for enum declaration cannot depend on a template "
> + "parameter, i.e., %qT", nested_name_specifier);
It can in, e.g.,
template <class T>
enum A<T>::E { ... };
We could hit this same ICE for anything that is not a class or
namespace, i.e. any of WILDCARD_TYPE_P. That's the problem here: the
nested-name-specifier on a definition needs to name a class or namespace.
Jason
next prev parent reply other threads:[~2015-10-21 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 14:40 Paolo Carlini
2015-10-21 19:24 ` Jason Merrill [this message]
2015-10-21 20:41 ` Paolo Carlini
2015-10-21 21:04 ` 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=5627E555.50405@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=paolo.carlini@oracle.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).