Refine Documentation on Verbatim Identifiers: Clarify @ Character Usage to Avoid Misinterpretation #43406
Conversation
This file contains 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
dotnet-policy-service
bot
added
the
community-contribution
BillWagner
approved these changes
Nov 12, 2024
There was a problem hiding this comment.
Thanks @shethaadit
I'll merge this as soon as the build finishes.
dotnet-policy-service
bot
added
the
okr-quality
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Updated Wording: Revised "isn't the part of a name" to "isn't part of the name," clarifying that
@is a syntactic marker, not included in the identifier name.Contextual Clarity: By updating the phrasing, we help readers better understand the behavior of the
@character in verbatim identifiers, which is essential for accurate comprehension of thenameofoperator.Fixes #43400
Internal previews