On 19 December 2013 23:29, Alex Russell <[email protected]> wrote: > Right, but number of objects you have to guard with anti-branding is much, > much larger. That argues against thenables pretty strongly, but again, I > don't think we need to change anything for ES6. We can repair this in ES7 if > it's a problem in practice.
I highly doubt that will be possible -- experience strongly suggests that every odd feature _will_ be relied on in the wild by that time. If we think thenable assimilation is a problem then we have to remove it now. I, for one, would welcome that. We could still provide an _explicit_ thenable adaptor method in the Promise API. /Andreas _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
