-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
Retarget to es6 and fix the resulting bugs #32221
Conversation
@typescript-bot perf test this - gotta see if/how re-targeting affects perf |
Heya @weswigham, I've started to run the perf test suite on this PR at 086e2c7. You can monitor the build here. It should now contribute to this PR's status checks. Update: The results are in! |
@weswigham Here they are:Comparison Report - master..32221
System
Hosts
Scenarios
|
Yick - there's substantial improvements in one or two places on one or two versions, but generally across the board worseness, especially on node 12. 🤷♂ Guess I'll just change the target for debugging locally then. |
@typescript-bot perf test this again, just to validate that those performance regressions aren't just because of the correctness changes |
Heya @weswigham, I've started to run the perf test suite on this PR at b982747. You can monitor the build here. It should now contribute to this PR's status checks. Update: The results are in! |
@weswigham Here they are:Comparison Report - master..32221
System
Hosts
Scenarios
|
uhhhh @rbuckton any idea why these changes would be affecting, eg, check time so much? There isn't a change to any object structures, nor any changes that should affect the checker here... |
@typescript-bot perf test this |
Heya @weswigham, I've started to run the perf test suite on this PR at 170aa05. You can monitor the build here. It should now contribute to this PR's status checks. Update: The results are in! |
@weswigham Here they are:Comparison Report - master..32221
System
Hosts
Scenarios
|
Fixes #32206
We had a couple TDZ bugs and a case where we
for ..in
'd over the keys of a class instance to make a wrapper for it (which doesn't work on real es6 classes since the methods are non-enumerable and on the prototype).We don't need to retarget to es6, per sey, but it does make debugging certain things a little bit nicer - notably classes and generators, and we don't have much keeping us targeting
es5
, since every runtime we test on is es6+.