Alice Ryhl

The receiver is used here: https://github.com/tokio-rs/mini-redis/blob/ebe4e1f33113d8e43a68199d04943b2581b33604/src/server.rs#L203-L207

I don't understand the question.

Here's another trace of the execution: ([gist](https://gist.github.com/rust-play/192143474059a26d7be21d5e568950bd)) ``` t2 SWAP LOCK 0 to 2 (acqrel) t2 LOAD DATA = 0 (relaxed) t2 STORE OBSERVED = 0 (mutex) t1 STORE DATA...

Actually, I underestimated the amount of prior discussion about this, though nothing appears to have happened on the topic in the past year.

The `bool` type is `Copy`, so there should be no issue with returning it by-value.

For the record, the original playground can be modified to compile like this: ```rust impl { fn decode(buf: &'p mut dyn Buf) -> Self { let x = buf.get_u8(); Self...

The issue here is that you can't do what you are trying to do with every implementor of `Buf`. Calling `advance` might invalidate the pointer returned by `bytes`, so to...

As far as I understand, this repository is abandoned. The main Tokio crate has built-in support for mocking the timer.

@ids1024 In principle that same complaint could be targeted at the `Stream` trait, which is quite a bit further towards stabilization.

This seems way more complicated than it needs to be. If we require the sink to have item type `&[u8]`, then the `poll_write` call could just do `poll_ready` and pass...