Different Executors for Different Transports

[MavenRain]

What I am discovering in our company's use of libp2p is that different executors for swarms work with different transports. When I use the MemoryTransport, the default executor will work, and I can create a swarm just using Swarm::new. If I use a transport constructed from TokioTcpConfig, then I must implement an (albeit simple) executor manually, to be added via SwarmBuilder::new. Is this by design?

[mxinden]

You are correct. When using TokioTcpConfig you need to provide an executor. See also #2230.

I am sorry you had to debug this yourself. To prevent others from hitting this issue as well, would you mind sending in a patch to the documentation?

Also in case you can think of a way to prevent this at compile time, comments in #2230 would be appreciated.

[MavenRain]

@mxinden I can look at making an edit to the documentation to draw attention to this, and will see about a compile-time solution.