Change: rename AsyncOneshotSendExt
to OneshotSender
, remove TokioOneShotSender
#1157
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.
Changelog
Change: rename
AsyncOneshotSendExt
toOneshotSender
, removeTokioOneShotSender
Removal of
TokioOneShotSender
: Previously,TokioOneShotSender(tokio::sync::oneshot::Sender)
was used toimplement
Debug
for a oneshot sender. Given thatDebug
implementation is not a mandatory requirement,
TokioOneShotSender
isno longer necessary and has been removed.
Rename
AsyncOneshotSendExt
toOneshotSender
: The renamingreflects a more streamlined and intuitive naming convention.
Upgrade tip:
AsyncOneshotSendExt
toOneshotSender
AsyncOneshotSendExt
andTokioOneShotSender
are introduced in AsyncRuntime::oneshot #1026This change is