Describe scoping rules for extension declaration type parameters and receiver parameter #9229
+163
−1
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
jjonescz
reviewed
Mar 18, 2025
AlekseyTs
reviewed
Mar 18, 2025
AlekseyTs
reviewed
Mar 18, 2025
AlekseyTs
reviewed
Mar 19, 2025
AlekseyTs
reviewed
Mar 20, 2025
| @@ -50,6 +50,38 @@ receiver_parameter // add | |||
| Extension declarations shall only be declared in non-generic, non-nested static classes. | |||
| It is an error for a type to be named `extension`. | |||
|
|
|||
| ### Scoping rules | |||
|
|
|||
| The type parameters and receiver parameter of an extension declaration are in scope within the body of the extension declaration. It is an error to refer to the receiver parameter from within a static member. It is an error for members to declare type parameters or parameters with the same name as a type parameter or receiver parameter of the extension declaration. | |||
There was a problem hiding this comment.
AlekseyTs
reviewed
Mar 20, 2025
| @@ -50,6 +50,38 @@ receiver_parameter // add | |||
| Extension declarations shall only be declared in non-generic, non-nested static classes. | |||
| It is an error for a type to be named `extension`. | |||
|
|
|||
| ### Scoping rules | |||
|
|
|||
| The type parameters and receiver parameter of an extension declaration are in scope within the body of the extension declaration. It is an error to refer to the receiver parameter from within a static member. It is an error for members to declare type parameters or parameters with the same name as a type parameter or receiver parameter of the extension declaration. | |||
There was a problem hiding this comment.
It is an error for members to declare type parameters or parameters with the same name as a type parameter or receiver parameter of the extension declaration.
I think it is worth mentioning that the same goes for local variables and local function declared directly by members (not inside lamndas or local functions)
AlekseyTs
added a commit
to AlekseyTs/roslyn
that referenced
this pull request
Mar 20, 2025
…e parameters See dotnet/csharplang#9229 (commit 9)
AlekseyTs
added a commit
to dotnet/roslyn
that referenced
this pull request
Mar 21, 2025
…e parameters (#77704) See dotnet/csharplang#9229 (commit 9)
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.
Based on LDM feedback, these are revised scoping rules for extension declarations.