Skip to content

Conversation

@AlekseyTs
Copy link
Contributor

Fixes #4615.

@gafter, @VSadov, @jaredpar, @agocke Please review.

@AlekseyTs
Copy link
Contributor Author

cc @TyOverby

@AlekseyTs
Copy link
Contributor Author

Ping. @gafter, @VSadov, @jaredpar, @agocke Please review.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why can this return null but not VisitExpression?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah I think I understand now why this works this way.

@jaredpar
Copy link
Member

👍

@VSadov
Copy link
Member

VSadov commented Sep 15, 2015

LGTM

AlekseyTs added a commit that referenced this pull request Sep 15, 2015
Properly handle conditional access combined with conditional method.
@AlekseyTs AlekseyTs merged commit 7d2e3d6 into dotnet:master Sep 15, 2015
github-actions bot pushed a commit that referenced this pull request Apr 1, 2025
Fixes #5199
Fixes #5160

We already had implementation and option based support to perform exception path analysis to handle all operations that can potentially throw an exception, and hence need flow analysis data at the point of operation to be merged with analysis data at start of reachable catch blocks from that operation. However, we were only performing this analysis post pass when flow analysis is looking at exceptions data. Now we do it for all analysis as this is required for more accurate input analysis data at start of catch and finally blocks.
NOTE: Fixing this issue led to an assert firing in CodeAnalysis dataflow operation visitor for an existing unit test, which has also been fixed in this PR
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants