v13.0.0: hex_conservative dep included twice

[benma]

rust-miniscript v13.0.0 depends on hex_conservative v1.0.0.
It also depends on bitcoin v0.32.6, which depends on hex_conservative v0.2.0.

So hex_conservative is compiled/included twice when using rust-miniscript.

It would be great if the common deps of rust-miniscript and rust-bitcoin would always be compatible.

[apoelstra]

hex-conservative 1.0 and 0.2 are basically completely different libraries. 1.0 has decoding and error types. 0.2 has encoding. There is little overlap between them.

If you'd like, you can file an issue on hex-conservative asking when the hell we are going to 1.0 the encoding stuff..

[tcharding]

I don't know the personal relationship between you two so cannot fully interpret this discussion. FWIW the version chaos has a long history. Please do file an issue. Its useful to come from a user as internally we have argued it to death. Also we need prodding to resolve it (in my mind anyway because its in the too-hard or can't-be-bothered basket right now).

[benma]

We vendor our Rust deps, and when I see a duplicate dep in the vendor folder, I usually assume it's needless binary bloat. In this case it seems this is not the case and the "duplication" is for a good reason, so I'll close this issue. Thanks for the clarification.

@tcharding Not sure what you mean by personal relationship and how to interpret this, there is none and I thought this issue was clear enough - apologies if that was not the case.

Please do file an issue.

For clarity, do you mean an issue besides this one, generally about duplicate dependency versions across the rust-bitcoin crates? The goal is quite simple it seems (but I am missing all the context from your internal arguing, so it probably is not as simple as it seems 😄 ) - when using any combination of all the rust-bitcoin/* crates at the latest released version, ideally there should be no duplicate dependencies. It's not been a big issue in practice, there were only a few instances of this in the past few years (e.g. this one).

[apoelstra]

@benma can you file an issue on the hex-conservative crate saying that the lack of encoding support in 1.0 is causing dependency bloat elsewhere?