Futures

Tab Atkins Jr. jackalmage at gmail.com
Wed Apr 24 08:34:12 PDT 2013


On Tue, Apr 23, 2013 at 10:38 PM, Brendan Eich <brendan at mozilla.com> wrote:
> Tab Atkins Jr. wrote:
>> I still think that burdening the
>> call-site with the need to pull a future out of the object like that
>> (even though, yes, the object itself will be optimized out by future
>> VMs) is too much.
>
>
> This started (for me) when you wrote:
>
>> It would be so nice if JS had multiple return values, so we could let
>> cancellable future-returning APIs just return a naked resolver as their
>> second value,
>
> But now that I've pointed out JS has multiple return values, you're not
> happy :-P.

Like I said, destructing probably takes the wind out of multiple
return values.  The fact that you answered "Multiple return values?"
with "Destructuring!" just confirms this.  ^_^

~TJ


More information about the es-discuss mailing list