395889c763
Rather than consuming `self` and returning `(Self, _)`. This did mean that a few crates that depended on `Ready` to own the `Service` and provide it once it was ready had to change to call `poll_ready` directly. Which in turn meant adding in some PhantomData<Request> so that the impl blocks wouldn't be under-constrainted. Take, for example: ``` impl<K, S: Service<Req>, Req> Future for UnreadyService<K, S> ``` would fail to compile with ``` error[E0207]: the type parameter `Req` is not constrained by the impl trait, self type, or predicates ``` |
||
|---|---|---|
| .. | ||
| src | ||
| tests | ||
| CHANGELOG.md | ||
| Cargo.toml | ||
| LICENSE | ||
| README.md | ||
README.md
Tower Spawn Ready
Spawn Ready ensures that its inner service is driven to readiness on an executor. Useful with pooling layers that may poll their inner service infrequently.
License
This project is licensed under the MIT license.
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in Tower by you, shall be licensed as MIT, without any additional terms or conditions.