Thomas Eizinger
Thomas Eizinger
## Description Whilst thinking about https://github.com/libp2p/rust-libp2p/issues/2863, I noticed that it is very easy to (accidentally) circumvent the limit on inbound substreams by "leaking" them to the `ConnectionHandler`. We do this...
## Description Rename the associated types of `ConnectionHandler` from `InEvent` to `FromBehaviour` and `OutEvent` to `ToBehaviour`. ## Motivation Using a `ConnectionHandler` outside of the `NetworkBehaviour` abstraction is generally possible put...
See the following discussion: https://github.com/libp2p/rust-libp2p/pull/2803#discussion_r956704249 TLDR: Tracking `Cargo.lock` would allow for greater visibility on how our dependencies change and might f.e. give us an earlier insight into bad semver bumps.
This is an initial step towards https://github.com/webrtc-rs/webrtc/issues/230. It is a brutal copy-paste from https://github.com/webrtc-rs/sctp/tree/proto over the current codebase. It doesn't compile because some of the APIs changed. My idea was...
1. We only use `futures-util`'s `alloc` feature in the tests. 2. `futures-core` only has one feature and that is alloc and it is on by default.
Fixes #170.
Follow-up from #133. Currently, `xtra::tick` does two things: 1. Fetch the next message from the mailbox 2. Pass the message to the actor (1) is already possible outside of `xtra::tick`...
A first implementation of a benchmark. Here are some first results: ``` increment/xtra/100 time: [940.73 us 969.06 us 998.71 us] increment/xtra/1000 time: [9.6542 ms 9.9258 ms 10.205 ms] increment/xtra/10000 time:...
@Restioson Mentioned in https://github.com/Restioson/xtra/pull/163#pullrequestreview-1068183473 that he'd like a workspace structure where the main `xtra` crate is moved into its own directory. I'd suggest that due to the large diff this...