We intend to soon ship both ES6 promises and weak collections unflagged in V8. Since the former depends on the latter, I'm combining both in this mail.
PROMISES Promises have been accepted into ES6, and have hit the draft spec earlier this year [1]. They are already used in DOM APIs. Mozilla also plans to ship promises in FF25. The current implementation of promises in Chrome lives in Blink, a V8-side implementation has been done last fall. We intend to ship Chrome 35 with the V8 implementation replacing the Blink one, since it is more up-to-date wrt the latest spec changes, and (we believe) more efficient. That means that V8 will turn on promises by default (they are currently being moved to es-staging). Owners: [email protected], [email protected] [1] http://people.mozilla.org/~jorendorff/es6-draft.html#sec-promise-objects WEAK COLLECTIONS Weak maps and sets have been in the ES6 draft for a long time [2, 3], and our implementation has been stable for years. Moreover, it is (under internal APIs) already used in shipping features, such as Object.observe. Our self-hosted implementation of promises uses ES6 weak maps internally. Due to this dependency, we are moving both features to staging simultaneously, and intend to ship them together. Owner: [email protected] [2] http://people.mozilla.org/~jorendorff/es6-draft.html#sec-weakmap-objects [3] http://people.mozilla.org/~jorendorff/es6-draft.html#sec-weakset-objects -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" 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.
