ced949cb6b
Until this commit, servers have required that `Service` and their `Future` to be `Send`, since the server needs to spawn some internal tasks to an executor, and by default, that is `tokio::spawn`, which could be spawning to a threadpool. This was true even if the user were certain there was no threadpool involved, and was instead using a different single-threaded runtime, like `tokio::runtime::current_thread`. This changes makes all the server pieces generic over an `E`, which is essentially `Executor<PrivateTypes<Server::Future>>`. There's a new set of internal traits, `H2Exec` and `NewSvcExec`, which allow for the type signature to only show the generics that the user is providing. The traits cannot be implemented explicitly, but there are blanket implementations for `E: Executor<SpecificType>`. If the user provides their own executor, it simply needs to have a generic `impl<F> Executor<F> for MyExec`. That impl can have bounds deciding whether to require `F: Send`. If the executor does require `Send`, and the `Service` futures are `!Send`, there will be compiler errors. To prevent a breaking change, all the types that gained the `E` generic have a default type set, which is the original `tokio::spawn` executor.
12 lines
243 B
Rust
12 lines
243 B
Rust
mod buf;
|
|
pub(crate) mod drain;
|
|
pub(crate) mod exec;
|
|
pub(crate) mod io;
|
|
mod lazy;
|
|
mod never;
|
|
|
|
pub(crate) use self::buf::StaticBuf;
|
|
pub(crate) use self::exec::Exec;
|
|
pub(crate) use self::lazy::{lazy, Started as Lazy};
|
|
pub use self::never::Never;
|