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

Re: [Futures] Possible to multiply-resolve a resolver in weird ways

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Wed, 05 Jun 2013 14:23:17 -0400
Message-ID: <51AF8215.3040907@mit.edu>
To: Anne van Kesteren <annevk@annevk.nl>
CC: DOM mailing list <www-dom@w3.org>
On 6/5/13 2:08 PM, Anne van Kesteren wrote:
> I now made the resolved flag checks on the public methods. The
> internal ones no longer have the check so API authors just have to be
> careful to avoid race conditions or use their own flag to prevent that
> from happening. This also required added a check in the Promise
> constructor.

Thanks, looks reasonable.

> (I also implemented the renaming from Future to Promise per TC39
> discussion and removed the done() method. We may or may not end up
> with some more minor changes, will try to keep this list posted.)

Thank you for not breaking the existing links.  ;)

Looks like the "new Future" in the example in section 4.1 and some 
newFuture bits in the non-normative box right above the prose for the 
Promise constructor got missed.

Received on Wednesday, 5 June 2013 18:23:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:37:02 UTC