Thomas Eizinger
Thomas Eizinger
Once https://github.com/libp2p/rust-libp2p/issues/2722 is complete, I would suggest we inline the `HandlerWrapper` component into the `swarm::Connection` struct. This will resolve some indirection which: - Allows us to use the incoming substream...
## Description We have a lot of custom `Either` types within `libp2p-core`, some of which (I think) could go away by implementing our traits directly on the `Either` type that...
1. Should all workspace dependencies express a version number? We currently sometimes include and sometimes we don't. 2. We mix two styles of depending on workspace crates: a. Depending on...
Are there any plans on natively supporting WebRTC, i.e. without compiling to WASM and running the whole thing in the browser to be able to use `js-libp2p-webrtc`? The usecase would...
### Steps to reproduce 1. Open the Element desktop app. 2. Observe no decorations (i.e. no close and minimize buttons, etc) ### Outcome #### What did you expect? A window...
Prior to this patch-set, we had constructs like `MessageType` and `SentMessage`. These were used to write code that is generic over a particular message type. In reality however, we don't...
This introduces a generic `ChanPtr` type which adds reference counting to the channel. This allows us to remove the `Sender` type and promote `inbox::Receiver` to a (future public) `Mailbox` type....
In case the user passes a capacity, we know how many elements we will be storing in those queues. We can initialise them directly with this capacity which avoids growing...
This is a PoC for #126. It didn't quite turn out the way I wanted but I am putting it up anyway so gather some feedback.
With https://github.com/Restioson/xtra/pull/85, we are introducing 3 mailboxes: ordered, prioritized and broadcast. Ordered exists because `BinaryHeaps` don't preserve insertion order and thus, messages with the same priority (like 0 as the...