-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Always report unmeasurable variance for mapped types #49894
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 e9b71d0. 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 e9b71d0. You can monitor the build here. |
Heya @ahejlsberg, I've started to run the parallelized Definitely Typed test suite on this PR at e9b71d0. You can monitor the build here. |
Heya @ahejlsberg, I've started to run the abridged perf test suite on this PR at e9b71d0. You can monitor the build here. Update: The results are in! |
@ahejlsberg Here they are:Comparison Report - main..49894
System
Hosts
Scenarios
Developer Information: |
Heya @ahejlsberg, I've run the RWC suite on this PR - assuming you're on the TS core team, you can view the resulting diff here. |
@ahejlsberg Here they are:Comparison Report - main..refs/pull/49894/merge fp-ts2 of 4 projects failed to build with the old tsc tsconfig.json
|
There's definitely some performance impact to this. Check time increases 2% in |
Hmm, yeah, some pretty bad effects in import { Collection} from "lodash";
declare let ca: Collection<any>;
declare let cs: Collection<string>;
ca = cs;
cs = ca; |
I'm going to close this PR as it simply isn't feasible from a performance perspective. |
Fixes #49852.