Switching to async/await from Task.jsm/yield
dtownsend at mozilla.com
Thu Mar 16 22:48:45 UTC 2017
It's pretty much drop in. The only slight difference I can think of is that
you can't "await" on a generator function like you could yield one before,
you must always await the result of an async function or a promise.
On Thu, Mar 16, 2017 at 3:39 PM, Mike Conley <mconley at mozilla.com> wrote:
> I'm all for it.
> For the people who are more familiar with async / await than I am, and
> have also used Task.jsm, are there any gotchas, or is it pretty much a
> drop-in replacement?
> On 2017-03-16 6:29 PM, Dave Townsend wrote:
> > For a long time now we've been writing JS code that waits for promises
> > using Task.jsm and generator functions. Recently though the JS team
> > added support for the JS standard way of doing this, async/await:
> > Writing code in standard JS is always better for the web, makes it
> > easier to onboard new engineers and allows for better support in
> > developer tools. So I'd like to propose that we switch to the standard
> > way of writing these functions immediately. New code should use
> > async/await instead of Task.jsm going forwards.
> > Florian has some rough plans to automatically rewrite existing usages of
> > Task.jsm to the standard JS forms so for now don't worry much about
> > going and submitting patches to fix up existing code. Once that is done
> > we can remove Task.jsm from the tree.
> > Does anyone object to any of this?
> > _______________________________________________
> > firefox-dev mailing list
> > firefox-dev at mozilla.org
> > https://mail.mozilla.org/listinfo/firefox-dev
> firefox-dev mailing list
> firefox-dev at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the firefox-dev