Re: [JS-internals] Changes to the Promise ES6 spec

2014-02-18 Thread Boris Zbarsky
On 2/18/14 10:59 AM, David Bruant wrote: What I meant was "it'd be excellent if Blink and Moz made the test suite more complete" Ah, OK. Yes, that would be a good idea. :) I guess contributing to the Promise/A+ repo works. Assuming they care about the subclassing issues and whatnot. Yes

Re: [JS-internals] Changes to the Promise ES6 spec

2014-02-18 Thread Brendan Eich
On Feb 18, 2014, at 11:52 AM, Ehsan Akhgari wrote: >> The current ES6 consensus needs to be nailed down harder, but I think it >> will stick. That it isn't compositional won't stop this. Promises were a >> library de-facto standard from CommonJS and other ecosystems; the >> committee erred in try

Re: [JS-internals] Changes to the Promise ES6 spec

2014-02-18 Thread Ehsan Akhgari
On 2/17/2014, 4:32 PM, Brendan Eich wrote: The problem is one V8 principal (among others in what I think is a clear minority) do not agree with the current consensus. The previous consensus was actually fractured, but no one worked through it and some amount of miscommunication, perhaps combined

Re: [JS-internals] Changes to the Promise ES6 spec

2014-02-18 Thread David Bruant
Le 18/02/2014 16:02, Boris Zbarsky a écrit : On 2/17/14 4:27 PM, David Bruant wrote: That said, it'd be excellent if Blink and Moz completed the current test suite (Promise/A+) Mozilla did, until we just removed cast(). Or at least we passed the test suite at http://domenic.me/aplus-tests-ag

Re: [JS-internals] Changes to the Promise ES6 spec

2014-02-18 Thread Boris Zbarsky
On 2/17/14 4:32 PM, Brendan Eich wrote: SpiderMonkey still needs to nativize the DOM/XPCOM-based implementation, both to follow the spec (including subclassability) The DOM can easily support subclassability once SpiderMonkey itself does. The problem is, SpiderMonkey has no subclassing suppor

Re: [JS-internals] Changes to the Promise ES6 spec

2014-02-18 Thread Boris Zbarsky
On 2/17/14 4:27 PM, David Bruant wrote: That said, it'd be excellent if Blink and Moz completed the current test suite (Promise/A+) Mozilla did, until we just removed cast(). Or at least we passed the test suite at http://domenic.me/aplus-tests-against-the-browser/ sure they implement the

Re: [JS-internals] Changes to the Promise ES6 spec

2014-02-17 Thread Brendan Eich
The problem is one V8 principal (among others in what I think is a clear minority) do not agree with the current consensus. The previous consensus was actually fractured, but no one worked through it and some amount of miscommunication, perhaps combined with "expansive" risk tolerance by some o

Re: [JS-internals] Changes to the Promise ES6 spec

2014-02-17 Thread David Bruant
Le 17/02/2014 21:56, Ehsan Akhgari a écrit : Hi everyone, We are on track to ship our Promise implementation in Firefox 29. Blink has already shipped their implementation on the stable channel of Chrome and they are facing difficulties determining whether they should change what they have shipp

[JS-internals] Changes to the Promise ES6 spec

2014-02-17 Thread Ehsan Akhgari
Hi everyone, We are on track to ship our Promise implementation in Firefox 29. Blink has already shipped their implementation on the stable channel of Chrome and they are facing difficulties determining whether they should change what they have shipped based on the recent ES6 changes to the Promi