aashish

Marking it as `unsafe` may be a bit much as it doesn't violate any of Rust's safety guarantees. I like the approach serde_json took to gate this function, which was...

Another option could be to add a [Deserializer::set_max_depth](https://docs.rs/rmp-serde/0.14.0/rmp_serde/decode/struct.Deserializer.html#method.set_max_depth) function as the Serde MessagePack library does.

> I think this crate already has to many features which cause problems because every new feature doubles the amount of build configurations. Sometimes the crate breaks if you have...

Does the example of bindings from Rust streams to Python async generators still exist? I saw that #21 was merged but that seems to be for the inverse use-case. Any...

Thanks for the pointers! I ended up just using a synchronous python generator instead as it wasn't critical to get this to be async on the python side. I may...

I'd love to take a stab at implementing this if noone is actively working on this!

Closing this, as I think I can work around this with `cwnd` from `Connection::stats()`.

With `portreuse` turned on, the [dial address](https://github.com/libp2p/rust-libp2p/blob/14938043cfb6c99a9fc9fb7f6fd3ecc4296b6329/transports/tcp/src/lib.rs#L479) is retrieved from [`PortReuse::local_dial_addr`](https://github.com/libp2p/rust-libp2p/blob/14938043cfb6c99a9fc9fb7f6fd3ecc4296b6329/transports/tcp/src/lib.rs#L131-L151) - which is always `Ipv4Addr::UNSPECIFIED`.

Hmm, the only possibility I can think of is to change port-reuse to bind to the listening address (including ip), but I saw that this was changed intentionally in #2382....

Sure! I've partitioned my loopback addresses locally into different subnets, eg `127.100.0.0/16`, `127.101.0.0/16`, `127.102.0.0/16`, etc. I've configured all traffic from `127.100.0.0/16` -> `127.100.0.0/16` to have latency _a_, `127.100.0.0/16` -> `127.101.0.0/16`...