Biagio Festa

@LPardue CI failures seem to not be related with the CR itself. Any updates on the review?

I had the same issue. I had another QUIC implementation that needed to communicate with `quiche` and, because of this bug, I could not have a client-server long-lived connection. So...

> `FragmentCollector::read_frame()` which use `async fn parse_frame_header` does not remember the read pointer, so if it is canceled in the middle, the data read from tcp stream will be forgotten...

Hi, thank you for reporting this issue. I was indeed able to replicate the problem. Unfortunately, this incompatibility is not directly produced in the `i3-autolayout` code, but in the third-party...

https://github.com/leshow/tokio-i3ipc/pull/47

I was waiting for the maintainer of the library releasing a new version. Unfortunately, it seems the project is not really active. Probably best option is to get dependency directly...

I agree `wtransport` should provide a simple API to access "chunk-read-operations". However, I am still investigating whether to make this more convenient and user-friendly (interoperability between ordered and no-ordered reads)....

I am not really inclined to implement `AsRef`/`AsMut` as I would like to not directly expose the lower layer. I want to let the access to QUIC layer only via...

> Why not? That's what I was implying - obviously these should only be available only with quinn enabled... Because they are standard traits. Standard traits are meant to provide...

> I'd actually suggest splitting the `wtransport` into two crates - one would be the all-guts-exposed low-level quinn-specific implementation, and the other would be sort of a higher-level details-hidden thing...