-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Replace errorType return with Debug fail in checkExpressionWorker #54117
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
base: main
Are you sure you want to change the base?
Conversation
@typescript-bot test this |
Heya @weswigham, I've started to run the diff-based top-repos suite on this PR at 7dfe497. You can monitor the build here. Update: The results are in! |
Heya @weswigham, I've started to run the extended test suite on this PR at 7dfe497. You can monitor the build here. |
Heya @weswigham, I've started to run the parallelized Definitely Typed test suite on this PR at 7dfe497. You can monitor the build here. Update: The results are in! |
Heya @weswigham, I've started to run the perf test suite on this PR at 7dfe497. You can monitor the build here. Update: The results are in! |
@weswigham Here they are:
CompilerComparison Report - main..54117
System
Hosts
Scenarios
TSServerComparison Report - main..54117
System
Hosts
Scenarios
StartupComparison Report - main..54117
System
Hosts
Scenarios
Developer Information: |
Hey @weswigham, the results of running the DT tests are ready. |
@weswigham Here are the results of running the top-repos suite comparing Everything looks good! |
case SyntaxKind.JsxNamespacedName: | ||
return errorType; // FIXME: Remove when JsxNamespacedName is no longer used as an expression | ||
case SyntaxKind.MissingDeclaration: | ||
return errorType; // invalid decorated expression |
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.
@rbuckton should this be an expression? It's not flagged by isExpressionNode
, but is definitely assigned to expression-expecting node positions.
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.
We have two different ways to test for expressions, so we may need to verify both are correct:
isExpression
in utilitiesPublic.ts — Tests whether aNode
is a subtype ofExpression
. Doesn't care about context (i.e., no.parent
access). Designed for use with transformers (where.parent
may not be set).isExpressionNode
in _utilities.ts — Tests whether aNode
is used in an expression position. Highly contextual (performs.parent
lookups). Used by the checker, though I'd love to find a way to retire it at some point.
@weswigham This looks like a strict improvement to me. Is there a reason not to merge this? |
Per my suggestion and this comment.