Paul Loyd

@darthur11 sorry for the late response. Assuming you're compiling in the release mode, none of your latencies are okay if destination actors aren't overloaded. Expected latency (if the destination is...

> I will keep this issue for a few days Yes, sure, feel free to ask more; I'll be happy to help you. > should be in micros or even...

> In other integrations repositories Which integrations?

I see the point of consistency, but you have some unique integrations. I'm not against renaming the main branch (although I have many local commands that depend on `master` naming...

This issue is about examples of connecting to HTTPS, not about providing self-signed certificates directly to the crate. If such functionality is highly desired, feel free to create a dedicated...

Yes =( It's exactly what I do: ```rust .bind(interval.start_time.as_rfc3339_weak()) ``` I don't think it's possible without specialization in Rust (what won't happen soon) to have a dedicated logic. Another way...

> You could remove the blanket S: Serialize implementation It's not obvious, because it's _very_ useful, and my production code relies heavily on it: we use a lot of wrappers...

Makes sense, possibly under dedicated `futures03` feature

#24 affects your case only if you want to use borrowed rows in `Stream` impl. They are fundamentally incompatible (anyone can call [StreamExt::buffered](https://docs.rs/futures/latest/futures/stream/trait.StreamExt.html#method.buffered)), only `T: for` can be used in...

And I'm sure we should avoid `async-stream`. It is a good implementation, but has disadvantages: * It's based on macro and isn't covered by `rustfmt` * It's based on TLS...