Add support for CancelToken?

[jasonkuhrt]

Hey,

Its probably too early to begin this in earnest but assuming most wants to play well in the spec-compliant world then would it make sense to add support for CancelTokens (detail) in any special way?

While cancelToken.promise is sufficient to feed combinators like until I wonder if anything special needs to be done on the error handling side to distinguish between a canceled stream versus a failed one.

[TylorS]

I can't speak for the other contributors, but I can say I'm not too interested in becoming spec-compliant. If we were to become spec-compliant, we would almost certainly see a performance drop.

[ospatil]

The cancelToken proposal has been withdrawn. More here - tc39/proposal-cancelable-promises#70.

[briancavalier]

Thanks @ospatil.

@jasonkuhrt I believe I can safely say that the consensus of the core most.js team has been that we wouldn't support CancelToken until it had become clear that it would survive and become official. Now that the proposal has been withdrawn, it doesn't make sense to support it in the core lib.

If someone needs support for it for some reason (CancelToken early adopters??), they can implement an external subscribe-like helper that deals with CTs.

[jasonkuhrt]

I discovered cancel tokens a mere few weeks ago, and now their out–ha. Sorry for the noise everyone.

[briancavalier]

No worries, @jasonkuhrt. Yeah, I think the withdraw was surprising to most folks. I haven't seen a good explanation for the reasons other than "google objected". I wasn't personally a fan of the proposal, but it'd be nice to know the reasons.