We don't have any use counters, but the names were rather obscure, and the ES2015 Promise conventions seem to have stuck more. I have not heard from any users which were in support of the old Promise API, but on the other hand, the fact that V8 does not currently meet the ES2015 Promise specification is a frequent complaint from both users and frameworks. There is no way to support both ES2015 Promise semantics per spec and Promise.prototype.chain at the same time.
Dan On Thu, Dec 10, 2015 at 2:57 PM, PhistucK <[email protected]> wrote: > Are there any use counters for them? Did you check whether they are used in > the wild? > (The HTTP archive can help here, or any internal Google index searching you > may have) > > > ☆PhistucK > > On Fri, Dec 11, 2015 at 12:50 AM, 'Daniel Ehrenberg' via blink-dev > <[email protected]> wrote: >> >> V8 had added a few functions for manipulating Promises which didn't >> make it into the ES2015 standard, namely Promise.prototype.chain, >> Promise.accept and Promise.defer. ES2015 specifies Promises in a way >> which is incompatible with some of these methods, and none of them >> appear to be on track to be included in a standard the future. >> >> I have added a flag to V8 and Chrome (--js-flags=--promise-extra) to >> retain the current additional promise features. I intend to flip the >> flag off by default in general within a few days, with the aim of V8 >> version 4.9 branching without additional Promise functions. >> >> Dan >> >> -- >> You received this message because you are subscribed to the Google Groups >> "blink-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> > -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
