feat!: Connection functions now return impl Future #108
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
Now that the MSRV is > 1.75 we can start making use of return position impl trait. We need to specify send bounds on the returned futures so we return an impl Trait, but it seems like rust is smart enough to allow us to use an actual async function in the implementations.
obmarg
force-pushed
the
obmarg/push-lqpvnynpvlwy
branch
from
6b1512d
to
ab70fe4
Compare
Merged
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.
Now that the MSRV is > 1.75 we can start making use of return position impl trait.
We need to specify send bounds on the returned futures so we return an impl Trait, but it seems like rust is smart enough to allow us to use an actual async function in the implementations.