> ...constantly manage the lifecycle of cancellation sources
Usually, you are passing through a runtime provided token (e.g. ASP.NET).
> ...constantly manage the lifecycle of cancellation sources
Usually, you are passing through a runtime provided token (e.g. ASP.NET).
Oh and oone more thing - the very (developer-managed) complexity makes it that people constantly got it wrong, usually just enough (as often with the case of threading) that it worked fine 90% of the time, and was very hard to make a case to management why we should invest effort into fixing it.
If you're writing a bare C# library for desktop deployment, you're managing your own cancellation sources.