Futures

Tab Atkins Jr. jackalmage at gmail.com
Fri Apr 26 12:29:07 PDT 2013


On Fri, Apr 26, 2013 at 12:24 PM, Alex Russell <slightlyoff at google.com> wrote:
> On Apr 26, 2013 8:33 PM, "Tab Atkins Jr." <jackalmage at gmail.com> wrote:
>> On Fri, Apr 26, 2013 at 11:25 AM, Kevin Smith <zenparsing at 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


More information about the es-discuss mailing list