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

Re: Deprecating Future's .then()

From: Sean Hogan <shogun70@westnet.com.au>
Date: Wed, 19 Jun 2013 15:31:42 +1000
Message-ID: <51C1423E.8030705@westnet.com.au>
To: "Mark S. Miller" <erights@google.com>
CC: "Tab Atkins Jr." <jackalmage@gmail.com>, "www-dom@w3.org" <www-dom@w3.org>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Anne van Kesteren <annevk@annevk.nl>
On 17/06/13 11:13 AM, Mark S. Miller wrote:
> Hi Sean, there's nothing undefined about this. It just doesn't do what 
> you might want.

Undefined might be the wrong word.

The point is that .then()/.catch() callbacks may return either
     a compatible Promise
or
     a value of any type, *with one exception* - an object with a 
.then() method.

A work-around was proposed, but it doesn't work with the current spec. 
Even AP2 wouldn't help in the general case.

I think the spec should explicitly state that addressing the exception 
is out of scope for Promises.

Sean
Received on Wednesday, 19 June 2013 05:32:15 UTC

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