David Barsky

For context, the Bevy reports that they incur about 10μs per each span/event when profiling.

The downside of this approach is that the use of a hard-coded offset _does not_ handle daylight savings. I feel that if we're to support non-UTC timestamps inside of tracing-appender,...

i want to make a few additional notes, but since i'm packing for my move this weekend, it might be a day or two. sorry!

Sorry, it's been a busy month. Do you mind if I make commits directly to your branch/fork for the changes that I think we need? Since I believe this approach...

I'm not opposed to this change (it is rather small...), but I'd like a little more detail about the motivations for this use-case, as I'm somewhat hesitant to make changes...

@hawkw mentioned in discord that she'd like a way to get a weak ref to a dispatcher, but noted that can be done in followup PR.

I think that Vector is the main public user of the re-exported prelude traits (see [this search](https://cs.github.com/?scopeName=All+repos&scope=&q=use+tracing_subscriber%3A%3Aprelude%3A%3A__tracing_subscriber_SubscriberExt%3B), cc: @tobz).

> I haven't gotten into the GitHub code search beta yet (just signed up), can you share a link that I can actually view? Ah, sorry about that. Here's [a...

Thanks! Can you format this PR to pass CI?

The issue is that `tracing-subscriber`'s `Registry` is a typemap for extensions and `tracing-opentelemetry` does not create distinct types that vary between different Layer instantiations. (can you also edit your bug...