Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specify the grammar formulations for attributes #65

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

llvm-beanz
Copy link
Collaborator

This does not exhaustively express all the places C++ attributes are valid, but it should cover enough detail to be useful.

Fixes #63.

This does not exhaustively express all the places C++ attributes are
valid, but it should cover enough detail to be useful.

Fixes microsoft#63.
@llvm-beanz llvm-beanz requested review from bogner, tex3d and pow2clk June 26, 2023 15:14
Copy link
Collaborator

@bogner bogner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. I have some minor editing notes that you can take or leave as you please.

all shared grammar elements between HLSL and C++. This spec attempts to detail
some of the grammar and parsing implications and will specify the process by
which existing attributes will convert to C++ attributes.
### Attribute Parsing
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Best to add a blank line before the section header for the benefit of those reading the markdown directly (I don't think it makes a difference in the rendered doc)

which existing attributes will convert to C++ attributes.
### Attribute Parsing

This proposal introduces new grammar formulations for parsing attributes
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd probably drop the word "new" - "introduces grammar formulations" is clear

```

In contrast to existing HLSL annotations and Microsoft-style attributes, these
attribute identifiers are case-sensitive `identifier` tokens.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is probably clear enough from context and I'm just being pedantic, but "attribute identifiers are case-sensitive identifier tokens" isn't strictly true (there's also the attribute-scoped-token formulation).

Maybe:

In contrast to existing HLSL annotations and Microsoft-style attributes, these formulations use case-sensitive identifier tokens

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Design Meeting Agenda item for the design meeting
Projects
Status: In Review
Development

Successfully merging this pull request may close these issues.

[0002] Specify attribute parsing grammar
2 participants