Ashley Mannix

@softprops That would be much nicer, but we've had trouble in the past attempting to wrangle new syntax into the macros, especially after the message string, because currently that whole...

@Kixunil No sweat! It looks like the `&dyn (std::error::Error + 'static)` type you've used in `slog` should be compatible with both `log` and `tracing`, which also use `&dyn (Error +...

> It would be useful to check experiences of any other programming language community. I'm not aware of any languages that have first-class, core-encouraged, structured logging support, but maybe there...

@dpc You're absolutely right that's an important point. And we expect a core Rust crate to cater to those use cases where performance is paramount. But how you capture properties...

At first I didn't really like the syntax of separating replaceable properties from other properties, because I see the message as just a view over the properties. But thinking about...

It is a bit of an unfortunate (mis)use of Cargo features, isn't it. Ideally I'd like to get away from the `max_level_*` features altogether in favor of an environment variable...

In general, I kind of suspect the majority of library build scripts could be killed off with some expanded `#[cfg]`s to detect Rust versions and target features / reachability. If...

As of `1.60.0` we'd be able to start using `#[cfg(target_has_atomic)]` so once we're ready to bump to that we'll be able to remove this build script.

Worth looking at the [C# YAML Tests](https://github.com/elastic/elasticsearch-net/tree/develop/src/Tests/Elasticsearch.Net.Integration.Yaml) for ideas on interpreting the YAML structure

This is going to depend on getting a YAML library working https://github.com/serde-rs/yaml/issues/3