3 ms·
Cargo will do its best to unify separate versions, but if it can't, then it will just include both. So it sounds like this would be a non-issue here.
by steveklabnik 10y ago
Cargo will do its best to unify separate versions, but if it can't, then it will just include both. So it sounds like this would be a non-issue here.
- coolsunglasses 10y ago>So it sounds like this would be a non-issue here. In the sense of being a sucking chest wound driving new people away, I agree. >just include both makes my guts wrench a bit though. I understand how you're (currently) getting away with it but yikes.
- steveklabnik 10y agoWhy would it drive people away? I read your thesis as "it's broken all the time so people don't like it", but I'm saying that it wouldn't be broken. EDIT: Apparently coolsunglasses was referring to the Platform, not Cargo, with this comment.
- viraptor 10y agohttps://github.com/rust-lang/cargo/issues/2064 https://github.com/rust-lang/cargo/issues/2064 From my perspective: one of the biggest issues in cargo right now. I know it's not the same as the HP problem, but current cargo is definitely not good at solving this.
- steveklabnik 10y agoYes, this has been a big thing we've been discussing a lot. Something will probably happen, but design work is still being done.