tower
tower copied to clipboard
tower-rs
async fn(Request) -> Result<Response, Error>
[`futures-lite`](https://docs.rs/futures-lite/latest/futures_lite/) is a subset of the `futures-util` crate that contains much less bloat and compiles an order of magnitude faster. I would like to look into replacing some of `futures`...
I am currently working on a project where middleware is applied bottom-up, i.e. the middleware is appended after the services (which is also the case in axum for example, where...
## Motivation Currently, many tower service wrappers and layers are limited to working with `'static` types, which limits its usefulness when working with non-`static`ally borrowed things to and from scoped...
Upgrade these dependencies to allow downstream users to reduce duplicate dependencies (specifically this makes `axum` CI fail for duplicate dependencies when upgrading to tower 0.5: https://github.com/tokio-rs/axum/actions/runs/10440315723/job/28910071844?pr=2880 )
Hello, I wasn't sure how to contribute to this project, so I hope this is a right place to start discussing. Basically this revision solves real problem that I had...
Switching from tower 0.4 to tower 0.5.0 in an application using axum, couldn't compile tower lib due to the following error : Compiling tower v0.5.0 error[E0015]: cannot call non-const fn...
Encountered in https://github.com/hyperium/hyper-util/pull/144
There's a warning about `Sealed` (in `tower`) not being used when default features are disabled, as seen here: https://github.com/tower-rs/tower/actions/runs/10373855535/job/28719943265#step:5:72 We should fix that.
