Futures

Kevin Smith zenparsing at gmail.com
Mon Apr 22 09:47:53 PDT 2013


> FWIW I disagree with him -- I strongly suspect that by the time this were
> to all go down and a stable polyfill existed there'd already be too much
> then-demanding code in the wild. There probably already is. And at that
> point it's __proto__ all over again -- the standard will have no choice but
> to respect then and the problem cannot be fixed :-/
>
>
Why not?  If the `then` symbol is well-known (e.g. easily imported from
somewhere), then why can't libraries be upgraded to use it as an alias for
their `then` method?

{ Kevin }
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20130422/097f530c/attachment-0001.html>


More information about the es-discuss mailing list