Clarify when "additional processing" of a named value occurs #631
Conversation
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
This change clarifies that when an implementation "performs additional processing" on the expression of a declaration, that expression must be a variable with no annotation.
eemeli
approved these changes
Feb 7, 2024
aphillips
requested changes
Feb 7, 2024
Co-authored-by: Addison Phillips <addisonI18N@gmail.com>
aphillips
approved these changes
Feb 7, 2024
|
fast-tracking as this is not a material change |
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 sugg
2D61
estions 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.
This change clarifies that when an implementation "performs additional processing" on the expression of a declaration, that expression must be a variable with no annotation.
This came up when discussing #589 and is a purely editorial change.