Re: Deprecating Future's .then()

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