It looks like the main concern raised about switching over to async/await where possible is bug 1242505. We're going to try to get some resources for fixing that bug and it probably blocks doing a mass rewrite of existing code but I don't think it blocks people starting to use async/await right now as we're already using native Promises in lots of places. So lets go ahead with this and avoid using Task.jsm in the future. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
- Re: Switching to async/await from Task.jsm/yi... Kris Maglione
- Re: Switching to async/await from Task.js... J. Ryan Stinnett
- Re: Switching to async/await from Tas... Michael Layzell
- Re: Switching to async/await fro... Kris Maglione
- Re: Switching to async/await from Task.jsm/yield Dave Townsend
- Re: Switching to async/await from Task.jsm/yield Kris Maglione
- Re: Switching to async/await from Task.jsm/yield Ehsan Akhgari
- Re: Switching to async/await from Task.jsm/yield Kris Maglione
- Re: Switching to async/await from Task.jsm/yi... Ehsan Akhgari
- Re: Switching to async/await from Task.js... Till Schneidereit
- Re: Switching to async/await from Tas... Dave Townsend
- Re: Switching to async/await fro... Kris Maglione
- Re: Switching to async/await fro... Florian Quèze
- Re: Switching to async/await... Sam Foster
- Re: Switching to async/await... Kris Maglione
- Re: Switching to async/await from Task.jsm/yield Paolo Amadini
- Re: Switching to async/await from Task.jsm/yield Joshua Cranmer 🐧
- Re: Switching to async/await from Task.jsm/yield Dave Townsend