-
Notifications
You must be signed in to change notification settings - Fork 12.9k
Fix control flow analysis in try-catch-finally #34880
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
Conversation
@typescript-bot test this |
Heya @ahejlsberg, I've started to run the extended test suite on this PR at f2b3e06. You can monitor the build here. It should now contribute to this PR's status checks. |
Heya @ahejlsberg, I've started to run the parallelized Definitely Typed test suite on this PR at f2b3e06. You can monitor the build here. It should now contribute to this PR's status checks. |
Heya @ahejlsberg, I've started to run the perf test suite on this PR at f2b3e06. You can monitor the build here. It should now contribute to this PR's status checks. Update: The results are in! |
@ahejlsberg Here they are:Comparison Report - master..34880
System
Hosts
Scenarios
|
Tests all look good (DT failures are pre-existing conditions). |
This PR revises our logic for building CFA graphs for try-catch-finally statements. Two changes are implemented by this PR:
try
block as a possible antecedent in the exception case. Now we only include CFA nodes representing assignments and array mutations.finally
block of exceptions in thecatch
block. We now do.Fixes #34797.