-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Add IteratorVoidReturnResult for optional 'value' when done #40825
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 perf test |
Heya @rbuckton, I've started to run the perf test suite on this PR at 52a09b6. You can monitor the build here. Update: The results are in! |
52a09b6
to
dad88fc
Compare
@rbuckton Here they are:Comparison Report - master..40825
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. |
These are the exact cases that illustrate why I'm not certain this approach will work compared to #40823: https://github.com/typescript-bot/TypeScript/pull/88/files#diff-f408a44c43eeedd5c1ee6356b6cda8b2 |
This experiment is pretty old, so I'm going to close it to reduce the number of open PRs. |
This is an alternative to #40823 to verify whether introducing an optional
IteratorVoidReturnResult
to theIteratorResult
union (that only applies whenTReturn
containsvoid
) will cause any issues with assignability in our user tests.Fixes #38479