Ashley Mannix

Hi @yoshuawuyts! :wave: Right now any release of `log` we publish will include this API under the `kv_unstable` feature gate, but we're not ready to commit to backwards compatibility just...

> In order to help test this feature, it would be nice if there was a release on crates.io with the ["kv_unstable"] feature available. For experimental technology such as async-log...

Ah yes that `Record::key_values` method is the way you can attach key-value pairs to a record in the absence of macro support. It needs to be a `&dyn Source`. Opening...

Having some standards around well-known key-value pairs is something I've also been exploring in [a little wrapper](https://github.com/KodrAus/antlog). It seems like it'll be useful for a more composable logging ecosystem.

> What if we move the Source::count to a separate trait @MOZGIII unfortunately a separate trait wouldn't really work because we'd lose the implementation when erasing as `dyn Source`. >...

I've spent a little time looking at how we could support attempting to coerce structured values to concrete types. This is something that would make logging frameworks that want to...

@yoshuawuyts and I discussed the path to stabilization for the kv support and came to the conclusion that there's really not much blocking calling the `kv` module stable and continuing...

Hey @softprops 👋 It would be pretty unfortunate for structured values to only support the unstructured `Debug` or `Display` outputs. I wrote a bit about `serde` in https://github.com/rust-lang/log/issues/388#issuecomment-629572564. The gist...

@softprops As far as I know it’s not something being actively worked on yet. If you’d like to take a look that would be great! Otherwise it was next on...

Hey @uazu! :wave: Sorry for taking so long to circle back and thanks for putting together your thoughts 😃 > If the Visitor only has one method, it would be...