-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
Allow variance annotations on generic references #56418
Allow variance annotations on generic references #56418
Conversation
@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 79e0c3a. 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 79e0c3a. You can monitor the build here. |
Heya @jakebailey, I've started to run the diff-based user code test suite on this PR at 79e0c3a. You can monitor the build here. Update: The results are in! |
Heya @jakebailey, I've started to run the parallelized Definitely Typed test suite on this PR at 79e0c3a. 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 79e0c3a. 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! |
Why does assignability change here if I replace interface with a type alias? namespace Interface {
interface InvariantArray<in out T> extends Array<T> { }
declare let arr: InvariantArray<unknown>
declare let brr: InvariantArray<number>
arr = brr // Variance annotations forbid this
brr = arr
}
namespace TypeAlias {
type InvariantArray<in out T> = Array<T>
declare let arr: InvariantArray<unknown>
declare let brr: InvariantArray<number>
arr = brr // For some reason this still works?
brr = arr
} |
Fixes #56390
Adds
ObjectFlags.Reference
to the allowed object flags, to encompass generic interfaces. Also adds tests to ensure that multi-layeredtype
references to object or primitive (number
) shapes still error only when they should.