feat: enable non-'static
where possible
#732
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 tasks (e.g.async-scoped
).Solution
Remove the
'static
restrictions where possible, mostly by introducing lifetime parameters.This change excludes
Buffer
andBufferLayer
which are more difficult to make non-'static
. It is possible to do by abstractingtokio::spawn
into a trait (whichasync_scoped::Scope
can also implement), this is also pending the publish of the recently merged tokio-rs/tokio#5665.