If an execution context's CancelToken component already contains a token, the execution context is not purged from the list of that token - like it does happen when you assign undefined - before the new token is assigned.
This would lead to very unfavourable behaviour I guess, having multiple tokens race to reject the PromiseToCancel.
domenic
commented
8 years ago
If an execution context's CancelToken component already contains a token, the execution context is not purged from the list of that token - like it does happen when you assign
undefined- before the new token is assigned. This would lead to very unfavourable behaviour I guess, having multiple tokens race to reject the PromiseToCancel.