- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Fri, 26 Apr 2013 12:29:07 -0700
- To: Alex Russell <slightlyoff@google.com>
- Cc: Kevin Smith <zenparsing@gmail.com>, Brendan Eich <brendan@mozilla.com>, EcmaScript <es-discuss@mozilla.org>, Norbert Lindenberg <w3@norbertlindenberg.com>, "Mark S. Miller" <erights@google.com>, Markus Lanthaler <markus.lanthaler@gmx.net>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Douglas Crockford <douglas@crockford.com>
On Fri, Apr 26, 2013 at 12:24 PM, Alex Russell <slightlyoff@google.com> wrote:
> On Apr 26, 2013 8:33 PM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote:
>> On Fri, Apr 26, 2013 at 11:25 AM, Kevin Smith <zenparsing@gmail.com>
>> wrote:
>> > Actually, I may have gotten it terribly wrong (apologies). In my
>> > prototype
>> > implementation, the following:
>> >
>> > Future.accept(Future.resolve(1)).then(value => {
>> >
>> > console.log(value !== 1);
>> > return Future.accept(Future.resolve(1));
>> >
>> > }).then(value => {
>> >
>> > console.log(value === 1);
>> > });
>> >
>> > logs
>> >
>> > - true
>> > - true
>> >
>> > Is that what it should be doing, according to the DOM spec? Anne, Alex?
>>
>> No, it should be "true", then "false".
>>
>> Future.resolve(1) returns a Future<1>.
>>
>> Future.accept(Future.resolve(1)) returns Future<Future<1>>.
>
> This would all be easier to discuss if you weren't writing using invented
> methods.
I'm using the methods defined in the Futures spec, because we're
talking about the behavior of Futures.
~TJ
Received on Friday, 26 April 2013 19:29:53 UTC