I run into different crates specifying different versions of same library and then causing build failures. Of-course carefully planning
Cargo.toml etc will avoid it, but I’m just trying to find out if these two things are possible:
<1> For any code published to the crates, can i see the source code from within the crate (
github repository link is what we write in
Cargo.toml so can be invalid as well) - so is there any inherent way to check the source code from what is there in
crates.io itself ?
cargo build first downloads the source and then compiles it if there is anything in Cargo.toml as
[dependencies] from crates.io. I am on linux. So is there anyway i can browse this downloaded source code ?