swarm: Deprecate futures::executor::ThreadPool
usage for connection tasks
#3107
Labels
decision-pending
Marks issues where a decision is pending before we can move forward.
getting-started
Issues that can be tackled if you don't know the internals of libp2p very well
help wanted
priority:nicetohave
Description
Currently, the default executor for connection tasks is a dedicated thread-pool created within the
SwarmBuilder
. With #3097, this is being made more explicit.As a follow-up we should deprecate the use of
ThreadPool
entirely.Motivation
Users of
rust-libp2p
will need to use some kind of async executor. They should use one of the new executor APIs introduced in #3097.Are you planning to do it yourself in a pull request?
Maybe.
The text was updated successfully, but these errors were encountered: