make the structs sync + send regardless of features enabled#53
Merged
Conversation
Owner
|
Can you provide a test to this use case? Or a gist with the broken code? |
Author
|
Hmm not sure how to write a test, since the offending code "just" doesn't compile, do you have a suggestion? The root of the problem is that tokio::spawn requires the given future to be A small example: use std::time::Duration;
async fn task() {
let builder = sql_query_builder::Select::new();
tokio::time::sleep(Duration::from_secs(1)).await; // future is not Send as this value is used across an await
builder.select("*");
}
#[tokio::main]
async fn main() {
tokio::spawn(async { // future cannot be sent between threads safely ...
task().await;
});
}If you don't enable the |
Author
|
Added tests |
belchior
reviewed
May 16, 2025
Author
|
Done |
belchior
approved these changes
May 18, 2025
Owner
This file contains hidden or 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
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.
Currently, the various select/update/... structs are only sync + send if you don't enable the
postgresqlor thesqlitefeatures.These two features add a
Vec<dyn WithQuery>property on the structs, which causes the struct to become !Send and !Sync. Apart from the surprise it causes, it also makes it hard to use in web framework handlers, because if any of these structs are held across an .await point, the future will also become !Send, which the web frameworks (like Axum) will reject.This PR adds the mentioned trait bounds, as far as I can see with no side effects.