-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explain semantics of multiple calls to CancellationTokenSource.Cancel
#11105
base: main
Are you sure you want to change the base?
Conversation
Also copy a line about LIFO semantics from one of the overloads, to unify the docs for each function.
Learn Build status updates of commit 5a2b566: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left some grammatical suggestions. Thanks!
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: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
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.