-
Notifications
You must be signed in to change notification settings - Fork 177
RUST-2166 Update convenient transactions API to use async closures #1372
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
RUST-2166 Update convenient transactions API to use async closures #1372
Conversation
@@ -99,6 +99,67 @@ impl<'a> Action for StartTransaction<&'a mut ClientSession> { | |||
} | |||
} | |||
|
|||
macro_rules! convenient_run { |
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.
The logic here is unchanged.
@@ -5,7 +5,7 @@ set -o errexit | |||
source ./.evergreen/env.sh | |||
|
|||
# Pin clippy to the latest version. This should be updated when new versions of Rust are released. | |||
CLIPPY_VERSION=1.84.0 | |||
CLIPPY_VERSION=1.85.0 |
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.
This was needed for clippy to accept the async closure syntax.
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.
the new async closures are so much nicer, lgtm!
RUST-2166
This adds the slightly-awkwardly-named-but-much-easier-to-use
and_run2
method, and updates almost all* of the callers to use the new method. It also pulls out the method body into a macro so rather than being duplicated across the async and sync (and now new-async) implementations it's shared across all three.* A couple of test operations ran into a rustc bug that mean they don't compile with the new method due to really fun
implementation of 'std::marker::Send' is not general enough
errors, so I left those with the old method. I think it pretty unlikely actual library users will run into this (the trigger condition here is the transaction closure capturing a value that has a manualSend
impl whenand_run2
is being called inside multiple layers of.box()
ed futures AFAICT).