W3C home > Mailing lists > Public > public-script-coord@w3.org > April to June 2013

Re: Deprecating Future's .then()

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 6 Jun 2013 09:56:23 +0900
Message-ID: <CAAWBYDBYA64t-mpEbnfny57mAWUu49t0Nj5m+y3+2Uv1oDnJgA@mail.gmail.com>
To: Sean Hogan <shogun70@westnet.com.au>
Cc: Anne van Kesteren <annevk@annevk.nl>, Sam Tobin-Hochstadt <samth@ccs.neu.edu>, "Mark S. Miller" <erights@google.com>, "www-dom@w3.org" <www-dom@w3.org>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Alex Russell <slightlyoff@google.com>
On Thu, Jun 6, 2013 at 9:51 AM, Sean Hogan <shogun70@westnet.com.au> wrote:
> Should the spec continue to allow this behavior?
>
> or ...
>
> Should the resolve algorithm - which is currently infinite unwrap for
> accepted / fulfilled futures - also be infinite unwrap for rejected futures?

I'm satisfied with either behavior.  It might be nice to have it
mirror the then/chain behavior, where it fully-unwraps or
single-unwraps as appropriate, but I'd likely be fine with both doing
single-unwrapping or both doing full-unwrapping.

~TJ
Received on Thursday, 6 June 2013 00:57:16 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:49 UTC