-
Notifications
You must be signed in to change notification settings - Fork 12.4k
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
Revert "Allow variance annotations on generic references (#56418)" #59793
Conversation
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.
the new assignability errors (for newly added assignments) are here the same as on main
- that's why those variance annotations that were allowed shouldn't be allowed (because they are completely ignored anyway)
@typescript-bot test it |
Hey @gabritto, the results of running the DT tests are ready. Everything looks the same! |
@gabritto Here are the results of running the user tests with tsc comparing Everything looks good! |
@gabritto Here they are:
tscComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
Developer Information: |
@gabritto Here are the results of running the top 400 repos with tsc comparing Everything looks good! |
Will this reopen #56390? |
If @RyanCavanaugh keeps the opinion that this is a bug then yes, it should be reopened. I could alternatively try to fix the assignability issue but it wasn’t clear to me if that should be fixed. So as the first step I decided that it’s better to have the checker rules in a cohesive state by reverting this PR and then hash out the desired behavior for this |
@typescript-bot test top800 |
@gabritto Here are the results of running the top 800 repos with tsc comparing Everything looks good! |
fixes #59790
see the comment here, cc @JoshuaKGoldberg @gabritto