Eliza Weisman

> Whenever we send an HTTP request, we would like to grab some fields from the current Span and send them along in the request, so the other side can...

Related: #824 (which also deals with adding `Value` implementations for more structured types).

In general, while this _sounds_ pretty simple, it's a pretty big issue, since it kind of depends on two tasks: - Make the `Value` trait user-implementable, and - Extend `Value`/`Visit`...

> I just merged in some refactoring to [`log`'s `Value` type](https://github.com/rust-lang/log/tree/master/src/kv/value) that you might find interesting. @hawkw that includes the const-fn based specialization we checked out a while ago. Very...

Another possible solution for supporting `serde` (and pretty much anything else, it turns out), while requiring a pretty minimal change to the existing `Value` system, is what @davidbarsky suggested on...

> * Add a feature to `tracing-fmt` to specify specific ordering for the `message` field, possibly an enum of `First | Last | Unordered`. > As a minor side note:...

I'm strongly in favour of more options for visualization. I think that broadly, we have two categories of options: 1. Write our own thing. This would take a bunch of...

I believe `tracing` and `tracing-core` should compile on these platforms with the `std` feature disabled (e.g. `default-features = false` in `Cargo.toml`). I believe the stdlib's `thread_local` macro, which is used...

If someone who's more familiar with wasm than I am is interested in helping out with this, please let me know — I'm happy to provide guidance on the `tracing`...

> > I believe the stdlib's `thread_local` macro, which is used when the `std` feature is enabled, is the only feature that `tracing` and `tracing-core` use that doesn't exist on...