Fix analyzer RCS1246 for conditional access expressions - #1772
Merged
josefpihrt merged 7 commits intoAug 8, 2026
Merged
Conversation
Contributor
Author
|
@dotnet-policy-service agree |
Contributor
Author
|
Hi, is there anything I could do to move this forward? |
josefpihrt
requested changes
Aug 1, 2026
Collaborator
|
@krajek Hey, thank you for your contribution and sorry for late review. |
…expression-analyzer-for-nullable-ireadonlylist # Conflicts: # ChangeLog.md
josefpihrt
approved these changes
Aug 8, 2026
This was referenced Aug 8, 2026
Closed
Open
This was referenced Aug 9, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Smallest reproducible program I could come up with:
new { Values = new int[0] }?.Values.ElementAt(0);Without the fix, the analyzer in that case throws NRE and fails the build.