-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Use type arguments instead of flags to detect variance marker types #35244
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 extended test suite on this PR at 9bb8c7f. You can monitor the build here. It should now contribute to this PR's status checks. |
Heya @ahejlsberg, I've started to run the perf test suite on this PR at 9bb8c7f. You can monitor the build here. It should now contribute to this PR's status checks. Update: The results are in! |
Heya @ahejlsberg, I've started to run the parallelized community code test suite on this PR at 9bb8c7f. You can monitor the build here. It should now contribute to this PR's status checks. |
Heya @ahejlsberg, I've started to run the parallelized Definitely Typed test suite on this PR at 9bb8c7f. You can monitor the build here. It should now contribute to this PR's status checks. |
@ahejlsberg Here they are:Comparison Report - master..35244
System
Hosts
Scenarios
|
The user suite test run you requested has finished and failed. I've opened a PR with the baseline diff from master. |
Community Test failures are just noise. However, in RWC tests we now OOM when compiling fp-ts (this is an old copy of fp-ts, the latest https://github.com/gcanti/fp-ts compiles fine). |
Closing this in favor of #35266. |
With this PR, we check the actual type arguments of type references or type aliases instead of using flags to detect marker types that are used by variance probing. Now, any type reference or type alias that contains a marker type in its type arguments will be compared structurally.
Fixes #33872.