Allow nonnull assertions in references for control flow #29351
Merged
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 #29344
Property and element accesses already dive into the nonnull version of the type (to reduce follow-on errors) to find a property type, so as far as the control flow references are concerned, a nonnull operator is a noop. While I was marking nonnull expressions as noop's for control flow reference matching, I went ahead and did the same for parenthesized expressions (so parens in the middle of a reference no longer prevent it from being control flow analyzed), since they are equally a noop.