Cargo: predictable dependency management

Re:Cargo: predictable dependency management by steveklabnik on Thursday May 05, 2016 @05:02PM (#11639647)

It doesn't have to do any renaming or modifying of names. Rust has a module system, so each dependency will use the version they need.

The only time it doesn't Just Work is if one of those crates re-exports a type from the sub-crate in a public manner, and then you try to call something from the other crate with a value of that type. You'll get a compile-time error about mismatched types.

[ Parent | on HN ]

Re:Cargo: predictable dependency management by cm3 on Thursday May 05, 2016 @05:07PM (#11639668)

But it sounds like that's what's going on. Using foo-1.1 in bar.rs and foo-2.2 in rabbit.rs.

[ Parent | on HN ]

Re:Cargo: predictable dependency management by steveklabnik on Thursday May 05, 2016 @05:11PM (#11639691)

Sure. That will Just Work in every case _except_ if bar and rabbit both re-export a type from foo, and you try to use them together. If they don't re-export anything, then it all works just fine. No renaming or transformations needed.

[ Parent | on HN ]