Explain semantics of multiple calls to `CancellationTokenSource.Cancel`
Also copy a line about LIFO semantics from one of the overloads, to unify the docs for each function.
Summary
Earlier today, I needed to perform several experiments to discover the semantics of CancellationTokenSource.Cancel, because they are undocumented.
I don't know the semantics of CancelAsync, so I haven't documented them.
Learn Build status updates of commit 5a2b566:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| xml/System.Threading/CancellationTokenSource.xml | :white_check_mark:Succeeded | View |
For more details, please refer to the build report.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
Some scope creep, but I've gone over every use of the word "will" in the file and replaced it with a present tense unless it's describing asynchrony or future actions.
Learn Build status updates of commit 8094c7a:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| xml/System.Threading/CancellationTokenSource.xml | :white_check_mark:Succeeded | View |
For more details, please refer to the build report.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel