-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
Don"t treat an instantiation expression as an assertion in skipOuterExpressions #59538
Conversation
@typescript-bot test it |
Looks like you"re introducing a change to the public API surface area. If this includes breaking changes, please document them on our wiki"s API Breaking Changes page. Also, please make sure @DanielRosenwasser and @RyanCavanaugh are aware of the changes, just as a heads up. |
Hey @jakebailey, the results of running the DT tests are ready. Everything looks the same! |
@jakebailey Here are the results of running the user tests with tsc comparing Everything looks good! |
@jakebailey Here they are:
tscComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
Developer Information: |
@jakebailey Here are the results of running the top 400 repos with tsc comparing Everything looks good! |
case SyntaxKind.ExpressionWithTypeArguments: | ||
return updateExpressionWithTypeArguments(outerExpression, expression, outerExpression.typeArguments); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#50820 added
ExpressionWithTypeArguments
toisOuterExpression
but treated it as an assertion, which then caused the checker to skip past it in reference checking. Split that out so we can skip past it in transforms like we did previously, which feels better because an instantiation is not really an assertion.Also, while here, fix the fact that other
OuterExpression
related code was notExpressionWithTypeArguments
either.Fixes #59535