Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[S.N.Quic] Observe exceptions in ResettableValueTaskSource #114226
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
[S.N.Quic] Observe exceptions in ResettableValueTaskSource #114226
Changes from 1 commit
d92daa7
00383c4
2c6cd10
9de51bb
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Just for the explanation: the
bool final = false
was here to have the "same" signature asTrySetResult
and in the past we did have non-final exceptions (from cancellation).It could have also gone the other way by making
final
mandatory to all calls toTrySetResult
andTrySetException
.Anyway, this is not a hill I want to die on, so keep the change as-is if you prefer it this way.
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 don't plan to do further refactors in this PR, just leaving my take: It would be better to make it mandatory on
TrySetResult()
so it's easier to see what the call sites are doing. We can add it back toTrySetException
when/if it turns out to be needed again, till then I don't see the value.