3 ms·
Wouldn't the library dependency hierarchy have been figured out during development in order to get it to a state that can compile? I'm assuming if you're pinnin
by belinder 3y ago
Wouldn't the library dependency hierarchy have been figured out during development in order to get it to a state that can compile? I'm assuming if you're pinning a dependency you already have something that compiles
- paholg 3y agoLet's say crate B depends on crate A with a pinned dependency, and uses one of its types in a public interface. Crate C depends on them both. It now can't bring in updates to A until B does, and when B updates that's a breaking change, so it better bump its major version. Take a look at this trick, for example, for foundational crates updating their major version: https://github.com/dtolnay/semver-trick https://github.com/dtolnay/semver-trick Now imagine that being an issue every single patch update.
- belinder 3y agoYeah I see what you mean, it's not so much about the first time it's deployed but for future updates where you want to update one dependency but another one requires it to stay the way it is