Ron Buckton (2014-08-18T23:16:19.000Z)
Domenic,

I like the addition that your version of `finally` can itself return a Promise, which I hadn't considered (as I hadn't had a need for it myself yet). Is the consensus that this won't make it into Promise until at least ES7, and then only if there's enough of a call for it?

To be honest, if ES7 has something like async/await then it won't need Promise.prototype.finally. Promise.prototype.finally is primarily a feature needed for Promises without async/await (e.g. in the ES6 timeframe, or ES7 if async/await is deferred to a later revision).

Ron
________________________________________
From: Domenic Denicola <domenic at domenicdenicola.com>
Sent: Monday, August 18, 2014 3:20 PM
To: Ron Buckton; EcmaScript
Subject: RE: Proposal: Promise.prototype.Finally

Here is the current design for Promise.prototype.finally. I agree it is a useful feature.


https://github.com/domenic/promises-unwrapping/issues/18
domenic at domenicdenicola.com (2014-08-22T21:33:15.672Z)
I like the addition that your version of `finally` can itself return a Promise, which I hadn't considered (as I hadn't had a need for it myself yet). Is the consensus that this won't make it into Promise until at least ES7, and then only if there's enough of a call for it?

To be honest, if ES7 has something like async/await then it won't need Promise.prototype.finally. Promise.prototype.finally is primarily a feature needed for Promises without async/await (e.g. in the ES6 timeframe, or ES7 if async/await is deferred to a later revision).