Elena Frank

+1 in favor of using more concrete names for associated types. Maybe we could instead of `FromBehaviour` name `InEvent` -> `ToHandler`. If we then also follow @thomaseizinger proposal to rename...

Related to this: What do you think about renaming `NetworkBehaviour::inject_event` -> `::inject_handler_msg` and `ConnectionHandler::inject_event` -> `inject_behaviour_msg` (or something similar). When first working with `NetworkBehaviour` and `Handler` as a user I...

> Yes, I think that makes sense. The only weird part is that FromSwarm will have a ConnectionHandler variant that will use the FromHandler event. Perhaps https://github.com/libp2p/rust-libp2p/pull/2867 should introduce two...

**Changelog** > Handle address change if a connection migrates - Moved to **Long-term**. For now we can simply disable connection migration.

**Changelog** `QuicMuxer` refactoring (elenaf9#6) was replaced and merged into #2289 with kpp#23: - Updated the status-quo description - Marked corresponding task as done.

**Changelog** > Evaluate whether we should switch to use `UdpSocket` from `quinn_udp` instead of the rust `std` implementation - For the first implementation we will stick with `UdpSocket` from rust...

**Changelog:** - [x] Finish remaining TODOs / FIXMEs in Libp2p quic third attempt #2289 - [x] Enhance docs - [x] Review how backpressure is enforced throughout the whole implementation ->...

Thank you for the detailed bug report @folex! I believe the issue is that when generating the out event the macro references the [`NetworkBehavour` ](https://docs.rs/libp2p/latest/libp2p/swarm/trait.NetworkBehaviour.html)**trait**, which you don't have imported:...

Fixed with #2932. Thanks @folex!

@hardliner66 @leenozara is solving this issue necessary before a new version is released? In this case I would implement it (if you are not already working on that yourself).