dpc

I will be happy to share my perspective and experiences during the discussion. Personally, I would be very happy to see as many features from `slog` ported to `log` so...

Good question. I'm aware that not everyone buys into the whole structured logging concept. Especially in `slog` where more "unusual" features are bundled together, people don't initially see the whole...

@bradleybeddoes I believe the part you're describing is called "contextual logging". I'm not sure if we should open another issue or consider it a part of this issue.

How is the performance of such structured logging proposals? "Message Templates" seems like it will involve string parsing/manipulations. Eg. It looks to me that `emit` is dynamically allocating `HashMap` every...

> chain a logger throughout your application This is a part of "contextual logging", and is orthogonal to structured logging provided by slog. One can use `slog-scope` and not worry...

Hmmm... I liked the fact that one does not have to repeat itself in `log("User {username} logged in from {ip_address}", username, ipAddress)` but maybe it is even better, since it's...

Also, how to support "additional" keyvalues? Eg. info!("a {whatisit} message! {ending}", whatisit="keyword", ending=":)", request_id=req_Id); The `request_id` is assigned to the key-value pairs, but is not actually used in textual message...

A lot of people asked for structured types in slog. Sadly it has many challenges. I didn't feel up to the task and just left it out. I think it's...

BTW. Structured types have been added to slog behind a feature flag. https://docs.rs/slog/2.1.1/slog/trait.Serializer.html#method.emit_serde . I'm not sure if that's the best way to do it, but since people continuously asked...

We have a list of active proof repositories here: https://github.com/crev-dev/cargo-crev/wiki/List-of-Proof-Repositories . Also - as long as you cross-trust your IDs, any person that trust any of you, will quite easily...