问题描述
我有以下(简化的)代码片段,我正试图在CpuPool上运行未来版本:
I have the following (simplified) code snippet and I'm trying to run a future on a CpuPool:
use futures::{self, Future, IntoFuture};
use std::error;
use futures_cpupool::CpuPool;
pub struct Store<T: 'static + Send + Sync> {
inner: Arc<StoreInner<T, C, SerDe, P>>,
}
struct StoreInner<T: 'static + Send + Sync> {
read_thread_pool: CpuPool,
}
impl<T: 'static + Send + Sync> Store<T> {
pub fn get(self, obj_id: String) -> Box<Future<Item = Arc<T>, Error = Box<error::Error + Send>>>
where
T: for<'de> BinaryDeserialize<'de>,
{
let latest_version_id =
futures::future::ok(()).and_then(move |_| self.get_latest_version_id(&obj_id));
let latest_version = latest_version_id.and_then(
move |version_id| -> Box<Future<Item = Arc<T>, Error = Box<error::Error + Send>>> {
self.get_version(&obj_id, version_id)
},
);
Box::new(self.inner.read_thread_pool.spawn(latest_version))
}
}
但是,尝试编译时出现以下错误.
However, I get the following error when I try to compile.
error[E0277]: the trait bound `futures::Future<Item=std::sync::Arc<T>, Error=std::boxed::Box<std::error::Error + std::marker::Send>>: std::marker::Send` is not satisfied
--> src/store/mod.rs:181:46
|
181 | Box::new(self.inner.read_thread_pool.spawn(Box::new(latest_version)))
| ^^^^^ `futures::Future<Item=std::sync::Arc<T>, Error=std::boxed::Box<std::error::Error + std::marker::Send>>` cannot be sent between threads safely
|
= help: the trait `std::marker::Send` is not implemented for `futures::Future<Item=std::sync::Arc<T>, Error=std::boxed::Box<std::error::Error + std::marker::Send>>`
= note: required because of the requirements on the impl of `std::marker::Send` for `std::ptr::Unique<futures::Future<Item=std::sync::Arc<T>, Error=std::boxed::Box<std::error::Error + std::marker::Send>>>`
= note: required because it appears within the type `std::boxed::Box<futures::Future<Item=std::sync::Arc<T>, Error=std::boxed::Box<std::error::Error + std::marker::Send>>>`
= note: required because it appears within the type `futures::future::chain::Chain<futures::AndThen<futures::FutureResult<(), std::boxed::Box<std::error::Error + std::marker::Send>>, std::boxed::Box<futures::Future<Item=serde::export::Option<std::string::String>, Error=std::boxed::Box<std::error::Error + std::marker::Send>>>, [closure@src/store/mod.rs:177:67: 177:115 self:_, obj_id:_]>, std::boxed::Box<futures::Future<Item=std::sync::Arc<T>, Error=std::boxed::Box<std::error::Error + std::marker::Send>>>, [closure@src/store/mod.rs:178:56: 180:10 self:_, obj_id:_]>`
= note: required because it appears within the type `futures::AndThen<futures::AndThen<futures::FutureResult<(), std::boxed::Box<std::error::Error + std::marker::Send>>, std::boxed::Box<futures::Future<Item=serde::export::Option<std::string::String>, Error=std::boxed::Box<std::error::Error + std::marker::Send>>>, [closure@src/store/mod.rs:177:67: 177:115 self:_, obj_id:_]>, std::boxed::Box<futures::Future<Item=std::sync::Arc<T>, Error=std::boxed::Box<std::error::Error + std::marker::Send>>>, [closure@src/store/mod.rs:178:56: 180:10 self:_, obj_id:_]>`
= note: required because of the requirements on the impl of `std::marker::Send` for `std::ptr::Unique<futures::AndThen<futures::AndThen<futures::FutureResult<(), std::boxed::Box<std::error::Error + std::marker::Send>>, std::boxed::Box<futures::Future<Item=serde::export::Option<std::string::String>, Error=std::boxed::Box<std::error::Error + std::marker::Send>>>, [closure@src/store/mod.rs:177:67: 177:115 self:_, obj_id:_]>, std::boxed::Box<futures::Future<Item=std::sync::Arc<T>, Error=std::boxed::Box<std::error::Error + std::marker::Send>>>, [closure@src/store/mod.rs:178:56: 180:10 self:_, obj_id:_]>>`
= note: required because it appears within the type `std::boxed::Box<futures::AndThen<futures::AndThen<futures::FutureResult<(), std::boxed::Box<std::error::Error + std::marker::Send>>, std::boxed::Box<futures::Future<Item=serde::export::Option<std::string::String>, Error=std::boxed::Box<std::error::Error + std::marker::Send>>>, [closure@src/store/mod.rs:177:67: 177:115 self:_, obj_id:_]>, std::boxed::Box<futures::Future<Item=std::sync::Arc<T>, Error=std::boxed::Box<std::error::Error + std::marker::Send>>>, [closure@src/store/mod.rs:178:56: 180:10 self:_, obj_id:_]>>`
代码看起来很纯真,将来的Item
和Error
均为Send
.我不知道为什么会收到这个错误.
The code looks innocent and both Item
and Error
in the future are Send
. I have no idea why I get this error.
推荐答案
我认为这里的问题是Future
特质不是Send
仅仅是因为其Item
和都是Send
-您必须明确指定它.
I think the problem here is that the Future
trait is not Send
just because its Item
and Error
are both Send
- you have to specify it explicitly.
如果Future
是一个结构,我认为编译器可以自动派生Send
,但是不是,所以不能.
If Future
was a struct, I think the compiler could automatically derive Send
, but it's not, so it can't.
我修复了编译错误,并将+ Send
添加到您已定义的Future
类型中,现在可以进行编译(除了没有main
函数的事实):
I fixed up the compilation errors and added + Send
to the the Future
types you've defined, and it now compiles (apart from the fact there's no main
function):
extern crate futures;
extern crate futures_cpupool;
use futures::Future;
use std::error;
use std::sync::Arc;
use futures_cpupool::CpuPool;
pub struct Store {
inner: Arc<StoreInner>,
}
struct StoreInner {
read_thread_pool: CpuPool,
}
impl Store {
pub fn get<T: 'static + Send + Sync>(
self,
obj_id: String,
) -> Box<Future<Item = Arc<T>, Error = Box<error::Error + Send>> + Send> {
let latest_version_id =
futures::future::ok(()).and_then(move |_| self.get_latest_version_id(&obj_id));
let latest_version =
latest_version_id
.and_then(
move |version_id| -> Box<
Future<Item = Arc<T>, Error = Box<error::Error + Send>> + Send,
> { self.get_version(&obj_id, version_id) },
);
Box::new(self.inner.read_thread_pool.spawn(latest_version))
}
pub fn get_latest_version_id(
&self,
obj_id: &String,
) -> Box<Future<Item = String, Error = Box<error::Error + Send>> + Send> {
unimplemented!();
}
pub fn get_version<T: 'static + Send + Sync>(
&self,
obj_id: &String,
version_id: String,
) -> Box<Future<Item = Arc<T>, Error = Box<error::Error + Send>> + Send> {
unimplemented!();
}
}
这篇关于特质绑定`futures :: Future< Item = Arc< T> ;, Error = Box< Error + Send>> ;: Send不满足的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!