Add configparser to Serialization

[Earnshhaw]

No description provided.

[djc]

On the one hand, 3.8M recent downloads seems somewhat popular, but I think the idiomatic approach would be using toml, which has 48M. It definitely doesn't belong in the section "Non-self-describing, no external schema file". Maybe there should be a new subsection within Serialization for self-describing formats (including config), which could have serde_json and toml?

[epage]

Would it also be worthwhile for a type of detailed comparison to link the serialization section to https://github.com/djkoloski/rust_serialization_benchmark ?

[djc]

Would it also be worthwhile for a type of detailed comparison to link the serialization section to https://github.com/djkoloski/rust_serialization_benchmark ?

Might make sense, though it doesn't really neatly fit into the existing structure.

[Earnshhaw]

On the one hand, 3.8M recent downloads seems somewhat popular, but I think the idiomatic approach would be using toml, which has 48M. It definitely doesn't belong in the section "Non-self-describing, no external schema file". Maybe there should be a new subsection within Serialization for self-describing formats (including config), which could have serde_json and toml?

Created a new subsection in Serialization and put configparser, toml and serde_json there.

[djc]

I don't think we want to guide users towards configparser, so I would not include it here. But ultimately I think that's for @nicoburns to decide.