Eliza Weisman

> Personally I think the proc macro crate version bump isn't really required (unless maybe if there was a period of time where using the crate directly _was_ the recommended...

wait, why do we even depend on this?

Yeah, I'm fine with adding a named error type, but this will require waiting for `tracing-subscriber` 0.4.

It looks like `cargo check` is failing on this branch because there are [merge conflicts which haven't been resolved](https://github.com/tokio-rs/tracing/blob/65a3c2b68e7aa336bd93823759cf90b2af988493/tracing-subscriber/benches/fmt.rs#L99-L153). Mind rebasing the latest master and fixing that?

Since this is a `tracing-core` change, it would be nice to get @carllerche's approval on this.

I'm definitely interested in this idea, as it seems like it has the potential to improve performance significantly when a collector wishes to implement specific behaviors only for a small...

See also existing issues #1939 and #1123 — this seems like a specific proposal for how to implement the behavior discussed in those issues. I believe the comments on those...

Answering some of the questions from above: @jebrosen > I believe it was, yes. That, and/or as a demonstration to users how Rocket's and users's `tracing` messages look as viewed...

> * ~The `rocket` library feature should be called `tracing` or similar.~ I see now that the `log` feature is for enabling compatibility with the `log` crate. It does not...

@siebertm Yeah, that appears to be the correct URL.