I’m wondering how Cargo mediates conflicts in dependency resolution? I did a bit of testing and found that if there’s a conflict, normally the newest patch version is selected, other wise another version of the same crate is included. Is there any thing else going on here?
Hi @abe! You can find a description of the dependency resolution algorithm here. There’s some talk about maybe someday switching over to a SAT solver, but I don’t think anyone’s really started work on that yet.