-
Notifications
You must be signed in to change notification settings - Fork 12.8k
No this
type arguments in base constraints
#54536
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 diff-based user code test suite on this PR at 9d570a0. You can monitor the build here. Update: The results are in! |
Heya @ahejlsberg, I've started to run the diff-based top-repos suite on this PR at 9d570a0. You can monitor the build here. Update: The results are in! |
Heya @ahejlsberg, I've started to run the abridged perf test suite on this PR at 9d570a0. You can monitor the build here. Update: The results are in! |
Heya @ahejlsberg, I've started to run the extended test suite on this PR at 9d570a0. You can monitor the build here. |
Heya @ahejlsberg, I've started to run the parallelized Definitely Typed test suite on this PR at 9d570a0. You can monitor the build here. Update: The results are in! |
@ahejlsberg Here they are:Comparison Report - main..54536
System
Hosts
Scenarios
Developer Information: |
@ahejlsberg Here are the results of running the user test suite comparing There were infrastructure failures potentially unrelated to your change:
Otherwise... Everything looks good! |
@ahejlsberg Here are the results of running the top-repos suite comparing Everything looks good! |
Hey @ahejlsberg, the results of running the DT tests are ready. |
This PR also fixes #54495 , cc @alecgibson |
@typescript-bot pack this |
Heya @DanielRosenwasser, I've started to run the tarball bundle task on this PR at 9d570a0. You can monitor the build here. |
Hey @DanielRosenwasser, 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 |
@typescript-bot user test tsserver |
Heya @DanielRosenwasser, I've started to run the diff-based top-repos suite (tsserver) on this PR at 9d570a0. You can monitor the build here. Update: The results are in! |
Heya @DanielRosenwasser, I've started to run the diff-based user code test suite (tsserver) on this PR at 9d570a0. You can monitor the build here. Update: The results are in! |
@DanielRosenwasser Here are the results of running the user test suite comparing Everything looks good! |
@DanielRosenwasser Here are the results of running the top-repos suite comparing Everything looks good! |
Apparently this is blocking ts-eslint from upgrading to 5.1; this is intended to be cherry-picked, right? @DanielRosenwasser |
Scratch that, it's actually #54542 (comment) |
!!! error TS2430: 'this' could be instantiated with an arbitrary type which could be unrelated to 'Set<T>'. | ||
!!! error TS2430: 'Set<T>' is assignable to the constraint of type 'this', but 'this' could be instantiated with a different subtype of constraint 'Set<T>'. |
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.
Well this is definitely an improvement. 😄
# Conflicts: # tests/baselines/reference/complexRecursiveCollections.errors.txt
@typescript-bot cherry-pick this to release-5.1 |
Heya @DanielRosenwasser, I've started to run the task to cherry-pick this into |
Hey @DanielRosenwasser, I couldn't open a PR with the cherry-pick. (You can check the log here). You may need to squash and pick this PR into release-5.1 manually. |
…o release-5.1 (#54814) Co-authored-by: Anders Hejlsberg <[email protected]>
This PR implements the following:
this
type argument to the reference. Instead,this
type arguments are only added when obtaining apparent types.With these changes, the repros in #54491 now type check faster than in 5.0.
Fixes #54491.
Fixes #54495.