QEDK
QEDK
Why is this needed @belak? Seems to be redundant with comment prefixes, we are not really aiming for API parity with Python `configparser`.
> Thanks for merging this! Thanks for the contribution!
> Hi! Can we have serde support in configparser? The question isn't _can_ but why? If you have a use-case for it, I think we can think about possibilities as...
> Yes. Hard typed structures is also a use case for us. This library is actually very hard to use and very verbose without some kind of derive based structure...
An easy way might be to use `serde_json`, parse our unparsed string and return the generic type? It is inefficient but doesn't require rebuilding the wheel. ~~ On Mon, 3...
You can just do `println!(config.writes())` or `println!(config.pretty_writes())`, no? Am I missing something?
@djve60 The underlying `impl` is a `HashMap` you can iterate over the keys by simply using the underlying hashmap. But you are correct, we should have a function to return...
@rylev The parser as it currently is, simply strips out anything in comments, empty lines and all of that - making a pure hash table, to put it simply, it...
> > > I totally get why this is not the default behavior. This is really just useful in the case of wanting to adopt an existing ini file. We're...
Closing this for now as unplanned.