You already do have that right; you can use any Promise implementation you choose, or none at all. You do *not*, however, typically have the "right" to alter what syntax does, and `async`/`await` explicitly chose that philosophy.
On Tue, May 5, 2020 at 11:37 PM medikoo <[email protected]> wrote: > Jordan Harband wrote > > Anything "more efficient" would likely not be spec compliant > > Promises (also those specified in ES) are quite opinionated, and I believe > we should have right to practice our own opinions in our own apps. > > On these grounds thenable objects (so not necessarily promise instances) > are > supported, and work seamlessly in promise chains. > > Unfortunately async/await breaks that support, it'll be great if we can > recover from that. > > > > -- > Sent from: > http://mozilla.6506.n7.nabble.com/Mozilla-ECMAScript-4-discussion-f89340.html > _______________________________________________ > 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
