-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Remove @@species lookup from Promise.all() and Promise.race() #151
Comments
|
@zloirock It would be consistent with, e.g., |
@claudepache it will be consistent, but only for me this approach seems strange? For |
We are going to remove @@species from promise.all and promise.race. PR's accepted! |
Um, we need an exact spec. There are two different uses of species in promise.all/race, as I described in the thread above. I made a proposal for how the two uses should be resolved; are you adopting my wording? |
In particular, the wording in https://esdiscuss.org/topic/resolve-reject-on-promise-subclasses-and-species#content-5 |
Fixes #151, per November 2015 TC39 meeting.
- RegExp.prototype[Symbol.split] calls ToUint32 (tc39/ecma262#92) - Species lookup removed from Promise.all and Promise.race (tc39/ecma262#151) - Generator functions are no longer constructors (tc39/ecma262#171) Fixes tc39#444
See https://esdiscuss.org/topic/resolve-reject-on-promise-subclasses-and-species
The text was updated successfully, but these errors were encountered: