W3C home > Mailing lists > Public > www-dom@w3.org > April to June 2013

Re: Future statics

From: Anne van Kesteren <annevk@annevk.nl>
Date: Fri, 5 Apr 2013 18:15:13 +0100
Message-ID: <CADnb78huDsDPCFS27aP3Qk-tGYuzFQPb_EH1uNp01DvAd1Y+Gw@mail.gmail.com>
To: Brandon Wallace <brandon.wallace@yahoo.com>
Cc: "www-dom@w3.org" <www-dom@w3.org>
On Fri, Apr 5, 2013 at 5:56 PM, Brandon Wallace
<brandon.wallace@yahoo.com> wrote:
> The example code in 4.1 references "Future.when()" but I don't see any
> definition for this method.

I forgot to rename it to Future.every.


> For Future.every() and Future.some(), I did not see anything requiring the
> order of the values array supplied to the callbacks should match the order
> of the futures supplied.  These methods will be harder to use without this
> requirement.

Clarified.


> A fourth static would be nice that behaves similar to Task.WhenAll() in the
> .Net Framework (1)
>
> Future.???() - Almost like 'every' except that it waits for all futures to
> complete and if any were rejected then rejects the future with an array of
> the rejection values.
>
> (1) http://msdn.microsoft.com/en-us/library/hh194874.aspx

If we continue the Array analogy this would be Future.map() I think.


--
http://annevankesteren.nl/
Received on Friday, 5 April 2013 17:15:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:20 UTC