fix: enter runtime context for now_or_never() within try_recv
#497
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The errors seem to be caused by new linting rule additions to clippy |
* Simplify code, remove `_guard` and create timeout within async closure * Add example usacases
carlocorradini
pushed a commit
to carlocorradini/rumqtt
that referenced
this pull request
Aug 3, 2023
…tebeamio#497) * fix: enter runtime context for `now_or_never()` * feat: cleanup code and add usage examples * Simplify code, remove `_guard` and create timeout within async closure * Add example use-cases * doc: add changelog for PR
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #496
Enter the runtime context within
Connection::try_recv()in order to allow the creation and passing of a noop waker for the instantaneous polling of associated future.