client: drop Send for non-wasm as well on response future
To see if it is even still necessary given that it's not a trait object type where auto traits would need to be explicit... Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
This commit is contained in:
parent
1531a619ab
commit
17f5eac57a
@ -20,9 +20,6 @@ use crate::{Authentication, Environment, Error, Token};
|
||||
/// An async [`Client`] requires some kind of async HTTP client implementation.
|
||||
pub trait HttpClient: Send + Sync {
|
||||
type Error: Error;
|
||||
#[cfg(not(target_arch = "wasm32"))]
|
||||
type ResponseFuture: Future<Output = Result<Response<Vec<u8>>, Self::Error>> + Send;
|
||||
#[cfg(target_arch = "wasm32")]
|
||||
type ResponseFuture: Future<Output = Result<Response<Vec<u8>>, Self::Error>>;
|
||||
|
||||
fn request(&self, request: Request<Vec<u8>>) -> Self::ResponseFuture;
|
||||
|
Loading…
x
Reference in New Issue
Block a user