Skip to content

Commit

Permalink
Remove '>' from sequence of tokens disambiguating type_argument_list
Browse files Browse the repository at this point in the history
Replacement for #1121 which I suspect was mistakenly closed. The original was approved back in May but merging seems to have slipped through the cracks – stuff happens.
  • Loading branch information
Nigel-Ecma authored Aug 23, 2024
1 parent a9257fc commit 285b76b
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion standard/lexical-structure.md
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,7 @@ The productions for *simple_name* ([§12.8.4](expressions.md#1284-simple-names))
If a sequence of tokens can be parsed (in context) as a *simple_name* ([§12.8.4](expressions.md#1284-simple-names)), *member_access* ([§12.8.7](expressions.md#1287-member-access)), or *pointer_member_access* ([§23.6.3](unsafe-code.md#2363-pointer-member-access)) ending with a *type_argument_list* ([§8.4.2](types.md#842-type-arguments)), the token immediately following the closing `>token is examined, to see if it is
- One of `( ) ] } : ; , . ? == != | ^ && || & [`; or
- One of the relational operators `< > <= >= is as`; or
- One of the relational operators `< <= >= is as`; or
- A contextual query keyword appearing inside a query expression; or
- In certain contexts, *identifier* is treated as a disambiguating token. Those contexts are where the sequence of tokens being disambiguated is immediately preceded by one of the keywords `is`, `case` or `out`, or arises while parsing the first element of a tuple literal (in which case the tokens are preceded by `(` or `:` and the identifier is followed by a `,`) or a subsequent element of a tuple literal.
Expand Down

0 comments on commit 285b76b

Please sign in to comment.