Matthias Beyer

> Its absence would be a bit of dealbreaker for me. Yes, to me too! > I didn't notice any issue with it while using the current config-rs, what's broken...

They do not maintain this package, I do :smile: No, writing back is still not possible, sorry.

Yes, the progress on this effort is rather stalled though. The more contributors, the better, you know? While at it, have a look at the "figment" crate. Not sure whether...

I just updated this PR because it had conflicts. Do we still want this?

Rebased, assuming we want this, so I'll merge after CI is green.

Hi. Does this issue still exist in later versions of this crate?

So the byte array above is parsed to this expression: ``` pM[22222222222222222]3 ``` Which is then parsed as a expression indexing `pM` at `22222222222222222` with `config::path::Expression::Subscript(/* some hex */, 22222222222222222)`....

So the original title of this PR does not apply anymore. The patches here only test whether log levels can be deserialized. I'll change the title accordingly. Still nice to...

> It seems like default values can be modeled as lower-level source and overrides can be modeled as a higher-level source. That's exactly the way I implemented it in the...

The progress can be seen here: https://github.com/matthiasbeyer/config-rs-ng/ but it is not near anything finished yet. Also, I am not sure whether it will be 0.14.0 or something down the road....