Allow accessing ref fields through rvalues #75316
Merged
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
AlekseyTs
reviewed
Oct 1, 2024
| // ref/out access to a ref field is fine regardless of the receiver | ||
| return true; | ||
| case RefKind.RefReadOnly: | ||
| ReportReadOnlyError(fieldSymbol, node, valueKind, checkingReceiver, diagnostics); |
There was a problem hiding this comment.
Good catch, this is unreachable code because there is an if (RequiresAssignableVariable(valueKind)) above which subsumes this one.
333fred
approved these changes
Oct 1, 2024
jaredpar
approved these changes
Oct 1, 2024
This was referenced Oct 9, 2024
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.
Fixes #75082.