Where'd Promise#done go?
Mark S. Miller
erights at google.com
Tue Jun 18 17:23:20 PDT 2013
I don't understand this. I am onboard with
and all that for better logging, and with using WeakRef notification to
improve the logging yet further. But I don't see how any of this can
substitute for the need that .done() serves. I think we will still need
.done() in ES7 promises.
Note: I didn't have .done() in E, but that's only because I didn't think of
it. I did have the problem that .done() addresses and I would have found it
On Tue, Jun 18, 2013 at 3:13 PM, Kris Kowal <kris.kowal at gmail.com> wrote:
> As Domenic mentions, there will be no place for "done" in our bright
> promise debugger future.
> It will however be necessary for promise users to keep on ending their
> chains with "done()" until promise debuggers are ubiquitously available.
> This is a simple problem. If you are writing code that targets both old and
> new engines, the promise polyfill will simply have to patch a no-op "done"
> onto the engine’s Promise.prototype.
> Kris Kowal
> es-discuss mailing list
> es-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss