Benjamin Saunders

I find the current behavior useful as well. It's pretty weird to write `let mut buf = &mut [0; 10]` instead of `let mut buf = [0; 10]` and then...

> Result We use this pattern heavily in quinn and it works great. We even have an extension trait for all `Buf` implementers to provide methods of that form for...

An alternative solution to this pattern is to have one slab, used to determine the index and maintain a freelist, and maintain `Vec`s on the side that share the same...

A convenient way to implement this would be a transaction-style adapter that stores the position at which it was constructed and can be either aborted or committed.

This seems handy, but so long as `bytes` is an extremely stability-sensitive interface crate I don't know if it should be accepting new self-contained interfaces. Perhaps this could be a...

> Mind elaborating on some of the motivating use cases here? It's common to want to support a graceful shutdown by returning control from the core after all work has...

No, `Handle::spawn` is routinely used for things like handling client requests.

A background task, in the sense used here, is a task that should not sustain the event loop, because it exists only to support the execution of foreground tasks. The...

> The fundamental issue right now is that a single core can be used by many independent libs and there is no way to signal shutdown. I think it's usually...

> On the other hand, serde-json is already depends on atoi crate. So for a user to write a microservice, these dependencies will be pulled in anyway. Note that not...