Highlight that contextual keywords cannot contain escapes. - #1755
Merged
Conversation
While reviewing #1696 I noticed that contextual keywords were not called out in prose as not allowing escapes. This does follow from the grammar as it does not allow them in *contextual_keyword* so calling them out in the prose isn't required. However maybe the list here reads as comprehensive even though its just an “e.g.” (not an “i.e.”), and calling it out seems harmless…
Nigel-Ecma
requested review from
BillWagner,
RexJaeschke,
ericlippert and
jskeet
July 25, 2026 23:46
RexJaeschke
approved these changes
Jul 28, 2026
RexJaeschke
left a comment
RexJaeschke
left a comment
Contributor
There was a problem hiding this comment.
LGTM, Nigel. BTW, at the very end of 6.4.4 Keywords, in the coverage of contextual keywords, we have the following Note:
Note: When used as contextual keywords, these identifiers cannot contain Unicode_Escape_Sequences. end note
BillWagner
approved these changes
Aug 3, 2026
BillWagner
left a comment
BillWagner
left a comment
Member
There was a problem hiding this comment.
I agree that this is a good change. It reinforces the rule.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While reviewing #1696 I noticed that contextual keywords were not called out in prose as not allowing escapes. This does follow from the grammar as it does not allow them in contextual_keyword so calling them out in the prose isn't required. However maybe the list here reads as comprehensive even though its just an “e.g.” (not an “i.e.”), and calling it out seems harmless…
Tagged as C#8 as it may help support PR #1696, even though it is not a required change.