Split iced_futures into different backend implementations
This commit is contained in:
parent
5dab5a327e
commit
167be45a7d
19 changed files with 280 additions and 318 deletions
|
|
@ -1,17 +0,0 @@
|
|||
use crate::Executor;
|
||||
|
||||
use futures::Future;
|
||||
|
||||
/// A thread pool runtime for futures.
|
||||
#[cfg_attr(docsrs, doc(cfg(feature = "thread-pool")))]
|
||||
pub type ThreadPool = futures::executor::ThreadPool;
|
||||
|
||||
impl Executor for futures::executor::ThreadPool {
|
||||
fn new() -> Result<Self, futures::io::Error> {
|
||||
futures::executor::ThreadPool::new()
|
||||
}
|
||||
|
||||
fn spawn(&self, future: impl Future<Output = ()> + Send + 'static) {
|
||||
self.spawn_ok(future);
|
||||
}
|
||||
}
|
||||
Loading…
Add table
Add a link
Reference in a new issue