Steven Fackler

That would handle part of it, but there's still the case where the logger is reconfiguring itself at runtime.

Yep, I definitely agree that it makes sense to allow Errors to be tacked onto log records - it will be a field that's only available with the `std` feature,...

You can configure your logging implementation to not output them if you'd like.

As long as it's possible to construct a `Record` via the public API (which we're going to support), a contextual logging library can be built on top of log without...

It's pretty straightforward to turn something like `{foo: some_variable, bar: "some_literal"}` into `&[("foo", &some_variable), ("bar", &"some_literal")]` in a normal macro-rules macro. I would very much like to keep the "normal"...

The next step would be to design the API. In particular, we need to figure out what the interface to the structured data is. We want the logging codepath to...

Cargo suppresses all warnings produced by dependencies, so even if we emitted a warning you wouldn't be able to see it in normal compilation contexts.

Might also be worth depending on https://crates.io/crates/jni-sys to avoid needing to have a second copy in here. Happy to make any changes necessary on that end.

I probably don't have the time to build out the high level wrapper right now unfortunately, so you might want to get it started.

A snippet from `readelf -s` where you can see an example of this: ``` 345: 00000000016077bc 92 FUNC LOCAL DEFAULT 13 _ZN4core3ptr71dr[...] 346: 00000000016077bc 0 NOTYPE LOCAL DEFAULT 13 $x.229...