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.
On Thu, Dec 19, 2013 at 2:21 PM, Gorgi Kosev <[email protected]> wrote: > > ...but only in an unpolyfillable, ES6-only world. >> >> > Right, they don't help existing libraries, but it would still pave a path > towards branded-only promises in the (unfortunately very, very far) future > (with ES5 all but gone) > > Only "ghetto anti-branding" will help existing libraries (and make it > possible to check if flipping the switch is okay much earlier). > > Its not like combining ghetto .then with ghetto `__notPromise__` is worse > than just ghetto `then`. One thing that can be done is to make it less > ugly. Since it would always be checked in tandem with `then`, it could > simply be `notConvertableToPromise`. Without the double underscores, > people will be slightly less likely to ask "what the hell were they smoking" > > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
