Eliza Weisman

> Would it make sense in the display to limit the amount of viewable bytes? That said, I think this makes sense to me. Yeah, we probably want to have...

> * Some of the parsing methods take `Bytes`, which is cheap to clone, or even just own, similar to the `TryFrom`. But those taking a slice, there'd be a...

To elaborate on the motivation here a bit, the particular use-case I'm thinking of with this feature request is one where the errors are being returned by a `hyper` server....

> > don't the parsing methods that take a slice convert the slice into a Bytes before trying to parse it, anyway? > > Uh, well, woops. That could be...

Quick ping on this, I'd be happy to open a PR to add it if we can come to consensus on the constraints!

Regarding abstracting over raw mutex types, I would encourage investigating whether the [`lock_api` crate](https://crates.io/crates/lock_api) can be used for that purpose --- it's pretty widespread in the non-embedded world, as `parking-lot`...

> * that the feature was defined in the top-level binary crate `Cargo.toml,` rather than a dependency library (if it's possible to tell, somehow?) I don't think there's really any...

> Instead, a user that wanted the static runtime would need to specifically start one (maybe w/ a `runtime::Builder` option). How is this noticeably different than `#[tokio::main]`? My understanding is...

> [This poll](https://users.rust-lang.org/t/poll-async-await-lets-talk-about-executors/31753) seems to indicate that in theory most people are in favor of explicitly passing things around, but in practice, the two big executors are global, and the...

> @hawkw Interesting. I admit I have not looked into the perf difference at all. I rarely write code so sensitive that passing a function param becomes an issue. This...