31–40 of 146 posts
How does Cargo manage the case when dependencies X and Y both require a different version of dependency Z?
It attempts to unify them if it can, but if they cannot be unified, it will include both versions.
I like many things about Rust, but Cargo alone is what initially got me started with it. I was in the process of setting up a fresh C++ project with vendored dependencies, and it was just an absolute nightmare. In contrast, it took me about 5 minutes to get a Rust project set up with comparable dependency complexity.
I like many things about Rust, but Cargo alone is what initially got me started with it. I was in the process of setting up a fresh C++ project with vendored dependencies, and it was just an absolute nightmare. In contrast, it took me about 5 minutes to get a Rust project set up with comparable dependency complexity.
Are there any big differences between Cargo and Python/Go/D/Ruby/Javascript/etc?
I see there is `cargo install` which will fetch and build an executable from crates.io, is there no `cargo update` for `install`?
I like many things about Rust, but Cargo alone is what initially got me started with it. I was in the process of setting up a fresh C++ project with vendored dependencies, and it was just an absolute nightmare. In contrast, it took me about 5 minutes to get a Rust project set up with comparable dependency complexity.
I understand that old languages like C++ or Java have problems providing a single package manager. It seems that newer languages have roughly equivalent services. Are there any big differences between Cargo and Python/Go/D/Ruby/Javascript/etc?
Earlier quoted context omitted.
It attempts to unify them if it can, but if they cannot be unified, it will include both versions.
Include both how? Make renamed copies to have two and modify the code to use the new names?
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.
Earlier quoted context omitted.
Include both how? Make renamed copies to have two and modify the code to use the new names?
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.
I see there is `cargo install` which will fetch and build an executable from crates.io, is there no `cargo update` for `install`?
https://github.com/rust-lang/cargo/pull/2405 landed, but https://github.com/rust-lang/cargo/issues/2082 is similar too and is still open.
Earlier quoted context omitted.
https://github.com/rust-lang/cargo/pull/2405 landed, but https://github.com/rust-lang/cargo/issues/2082 is similar too and is still open.
Interesting, but I was thinking more of something like "update installed binaries with latest version from index". This doesn't look like it.