Make toml_edit viable for cargo

[epage]

• add support for toml 1.0 #58
• Support parsing all Cargo.toml files #130
• Remove chrono from the public API #131
• toml-rs API on top of toml_edit #129
• Performance test against toml-rs #132

We might also need

• toml_edit doesn't properly handle quotes in strings #128
• easy::to_string_pretty doesn't produce pretty results #192
• Allow inserting serde types as values #205

[epage]

@ordian as I go through this, how much design review or PR review involvement do you want? So far I've been going ahead and merging-and-moving on for small things like comment fixes and for everything else I've been floating the design and PR by you. Just wondering if what you feel you need in case there is wiggle room to expedite cycle time a bit (since a lot of changes have risk of conflict heavy, I've been task switching rather than continuing on)

[ordian]

I added you as a collaborator on this repo, so you can merge stuff you find not controversial. I'm happy to provide feedback on the design of API for dotted keys as it seems like a big and not an easy one. But other than that feel free to merge as if this repo was cargo-release :)

[epage]

Thanks for the clarification; I didn't want to overstep any boundaries.

[epage]

We now have a tag for this instead: https://github.com/ordian/toml_edit/labels/cargo