From: Jason Merrill <jason@redhat.com>
To: Matthias Kretz <m.kretz@gsi.de>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Add gnu::diagnose_as attribute
Date: Wed, 7 Jul 2021 21:19:28 -0400 [thread overview]
Message-ID: <e92419b1-6627-f8b4-4629-1fdd23f5f2b1@redhat.com> (raw)
In-Reply-To: <18863746.PYa122fH2K@excalibur>
On 7/7/21 4:23 AM, Matthias Kretz wrote:
> On Tuesday, 22 June 2021 21:52:16 CEST Jason Merrill wrote:
>>> 2. About the namespace aliases: IIUC an attribute would currently be
>>> rejected because of the C++ grammar. Do you want to make it valid before
>>> WG21 officially decides how to proceed? And if you have a pointer for me
>>> where I'd have to adjust the grammar rules, that'd help.
>>
>> You will want to adjust cp_parser_namespace_alias_definition to handle
>> attributes like cp_parser_namespace_definition. The latter currently
>> accepts attributes both before and after the name, which seems like a
>> good pattern to follow so it doesn't matter which WG21 chooses.
>> Probably best to pedwarn about C++11 attributes in both locations for
>> now, not just after.
>
> This introduces an ambiguity in cp_parser_declaration. The function has to
> decide whether to call cp_parser_namespace_definition or fall back to
> cp_parser_block_declaration (which calls
> cp_parser_namespace_alias_definition). But now the parser has to look ahead a
> lot farther:
>
> namespace foo [[whatever]] {}
> namespace bar [[whatever]] = foo;
>
> I.e. only at '{' vs. '=' can cp_parser_declaration decide to call
> cp_parser_namespace_definition.
>
> Consequently, should I really modify cp_parser_namespace_definition to handle
> namespace aliases?
aliases can also appear at block scope, unlike namespace definitions,
but you could factor out some of the alias handling to call from both
places.
> Or can/should cp_parser_declaration look ahead behind the
> attribute(s)? How?
cp_parser_skip_attributes_opt
Jason
prev parent reply other threads:[~2021-07-08 1:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <14205410.xuKvIAzr1H@excalibur>
[not found] ` <20210427094648.GL3008@redhat.com>
2021-05-04 11:13 ` Matthias Kretz
2021-05-04 13:34 ` David Malcolm
2021-05-04 14:23 ` Matthias Kretz
2021-05-04 14:32 ` Matthias Kretz
2021-05-04 19:00 ` David Malcolm
2021-05-04 19:22 ` Matthias Kretz
2021-05-14 16:05 ` Martin Sebor
2021-05-26 21:33 ` Matthias Kretz
2021-05-27 17:39 ` Jason Merrill
2021-05-27 18:54 ` Matthias Kretz
2021-05-27 21:15 ` Jason Merrill
2021-05-27 22:07 ` Matthias Kretz
2021-05-28 3:05 ` Jason Merrill
2021-05-28 7:42 ` Matthias Kretz
2021-06-01 19:12 ` Jason Merrill
2021-06-01 21:01 ` Matthias Kretz
2021-06-11 10:01 ` Matthias Kretz
2021-06-15 15:51 ` Jason Merrill
2021-06-15 20:56 ` Matthias Kretz
2021-06-16 0:48 ` Jason Merrill
2021-06-22 7:30 ` Matthias Kretz
2021-06-22 19:52 ` Jason Merrill
2021-06-22 20:01 ` Matthias Kretz
2021-06-22 20:12 ` Jason Merrill
2021-07-01 9:28 ` Matthias Kretz
2021-07-01 15:18 ` Jason Merrill
2021-07-05 14:18 ` Matthias Kretz
2021-07-07 22:34 ` Jason Merrill
2021-07-07 8:23 ` Matthias Kretz
2021-07-08 1:19 ` 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=e92419b1-6627-f8b4-4629-1fdd23f5f2b1@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=m.kretz@gsi.de \
/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).