-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suppress ref readonly
warnings for collection initializers
#69307
Merged
jjonescz
merged 2 commits into
dotnet:main
from
jjonescz:RefReadonly-23-CollectionInitializer
Aug 10, 2023
Merged
Suppress ref readonly
warnings for collection initializers
#69307
jjonescz
merged 2 commits into
dotnet:main
from
jjonescz:RefReadonly-23-CollectionInitializer
Aug 10, 2023
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-issue-labeler
bot
added
Area-Compilers
untriaged
Issues and PRs which have not yet been triaged by a lead
labels
Aug 1, 2023
jjonescz
commented
Aug 1, 2023
@@ -145,7 +145,7 @@ private BoundExpression MakeDynamicCollectionInitializer(BoundExpression rewritt | |||
Debug.Assert(addMethod.Name == "Add"); | |||
Debug.Assert(addMethod.Parameters | |||
.Skip(addMethod.IsExtensionMethod ? 1 : 0) | |||
.All(p => p.RefKind == RefKind.None || p.RefKind == RefKind.In)); | |||
.All(p => p.RefKind is RefKind.None or RefKind.In or RefKind.RefReadOnlyParameter)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that this change is already included in parallel PR 8beb44d.
jcouv
approved these changes
Aug 1, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM Thanks (iteration 1)
jcouv
removed
the
untriaged
Issues and PRs which have not yet been triaged by a lead
label
Aug 1, 2023
@dotnet/roslyn-compiler for a second review, thanks |
jaredpar
approved these changes
Aug 9, 2023
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.
Inspired by similar changes for interpolated string handlers and extension method receivers.
Speclet change: dotnet/csharplang@8e5c156
Test plan: #68056