-
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
Narrow down non-const enity name expressions within element access expressions #56392
Narrow down non-const enity name expressions within element access expressions #56392
Conversation
Fails the self check so I'm going to assume that it'll break in testing; can run once you've had a chance to look. |
To be clear, this isn't a general fix for #56389, correct? |
Yeah, it isn't. I specifically only looked into what @DetachHead mentioned here |
…-entity-name-expressions-in-element-accesses
@jakebailey I fixed the |
if (rootDeclaration.kind !== SyntaxKind.VariableDeclaration) { | ||
return true; | ||
} |
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.
TODO: recheck correctness here
@typescript-bot test top200 @typescript-bot perf test this |
Heya @jakebailey, I've started to run the regular perf test suite on this PR at 5d49f98. You can monitor the build here. Update: The results are in! |
Heya @jakebailey, I've started to run the diff-based top-repos suite on this PR at 5d49f98. You can monitor the build here. Update: The results are in! |
Heya @jakebailey, I've started to run the diff-based user code test suite on this PR at 5d49f98. You can monitor the build here. Update: The results are in! |
Heya @jakebailey, I've started to run the tarball bundle task on this PR at 5d49f98. You can monitor the build here. |
Heya @jakebailey, I've started to run the parallelized Definitely Typed test suite on this PR at 5d49f98. You can monitor the build here. Update: The results are in! |
Hey @jakebailey, I've packed this into an installable tgz. You can install it for testing by referencing it in your
and then running There is also a playground for this build and an npm module you can use via |
@jakebailey Here are the results of running the user test suite comparing There were infrastructure failures potentially unrelated to your change:
Otherwise... Something interesting changed - please have a look. Details
|
@jakebailey Here they are:
CompilerComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
tsserverComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
StartupComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
Developer Information: |
Hey @jakebailey, the results of running the DT tests are ready. |
@jakebailey Here are the results of running the top-repos suite comparing Everything looks good! |
superseded by #57847 |
an experiment to fix #51368 . I wonder what the perf tests show for this (cc @jakebailey ) 😉