Even w/cancelable objects, however, we typically kept the authority to cancel a distinct capability. E.g. (resolve, reject, cancel).
-
-
also need to make sure it's possible to convey to combinators like Promise.all. Perhaps enough to immediate invoke async func
-
thing I like about `task`: it creates a notion of task that isn't just some combo of promises.
End of conversation
New conversation -
-
-
I understand separable capabilities. But I'd argue an awaits function already controls resolve/reject "outcomes" so cancellation ok.
-
One subtle distinction is that the token could be remembered beyond the call. In that way, maybe diff't than resolve/reject.
-
await.cancel is just the receiving end right? No new caps.
-
Ah yes, of course. The only new "ability" of callees would be subscribing to cancellation, which seems harmless...
-
passing it into the function constructor would be passing the sending side in (the capability).
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.