doc: mention that types are not interpreted

[mathstuf]

Closes: #87

[davvid]

FWIW I've merged this into my fork: https://github.com/davvid/yaml-rust

[mathstuf]

Thanks! Have you reached out about adopting the crate or republishing under another name (I see you've used your username at least but I'm not sure what that means for the maintenance plan, if any). Basically do you think it worth adding support for it in yaml-merge-keys?

And neat seeing you around the Rust world; I originally packaged git-cola for Fedora years and years ago…whew GIt says 14 of them.

[davvid]

Hi @mathstuf great crossing paths again. Attempts to reach out in #192 and other issues haven't gone anywhere so I don't think anyone will be taking over the original crates.io project anytime soon.

I have been publishing new versions, though. https://crates.io/crates/yaml-rust-davvid

It's easy for downstream projects to switch to this (or any other) fork because Cargo.toml lets you specify the package separately from the crate namespace:

[dependencies]
yaml-rust = { version = "0.6", package = "yaml-rust-davvid" }

This lets you use the original yaml_rust::* namespace. No other references to the fork end up in the code.

Adding support in yaml-merge-keys would be pretty cool from the perspective of using a safe, pure-Rust yaml implementation.

[mathstuf]

This lets you use the original yaml_rust::* namespace. No other references to the fork end up in the code.

Alas, all consumers also need to move to use this too in their Cargo.toml. However, yaml-merge-keys is pre-1.0, so a "major" break is "just" 0.7. I've opened an issue in the meantime.