Cargo dependency management in Rust - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Cargo.toml dependency version resolution?

Given the following Cargo.toml snippet, what version of serde will Cargo use?

[dependencies]
serde = "^1.0.100"
serde_derive = "1.0.104"

Assume no other dependencies affect serde.

A 1.0.100

B 1.0.104

C 1.0.99

D 1.0.105

💡 Hint

Check how Cargo resolves compatible versions with caret requirements.

Caret requirements like ^1.0.100 allow versions >=1.0.100 and <2.0.0. Cargo picks the highest compatible version. Since serde_derive requires 1.0.104, Cargo uses 1.0.104 for both.

🧠 Conceptual

intermediate

Which Cargo command updates dependencies to the latest compatible versions?

You want to update your Rust project's dependencies to the latest versions allowed by your Cargo.toml constraints. Which command should you run?

A cargo update

B cargo refresh

C cargo build --update

D cargo upgrade

💡 Hint

Think about the official Cargo command that updates the lock file.

cargo update updates the Cargo.lock file to the latest versions allowed by Cargo.toml. cargo upgrade is from an external tool, not built-in.

🔧 Debug

advanced

Why does this Cargo build fail with a version conflict error?

Consider a Rust project with these dependencies in Cargo.toml:

[dependencies]
foo = "1.2.0"
bar = "2.0.0"

Both foo and bar depend on different incompatible versions of baz. What is the most likely cause of the build failure?

A The <code>baz</code> crate is unpublished and cannot be downloaded.

B The <code>Cargo.toml</code> file is missing a <code>[workspace]</code> section.

C Cargo cannot unify incompatible versions of <code>baz</code> required by <code>foo</code> and <code>bar</code>.

D The Rust compiler version is too old to build <code>foo</code> and <code>bar</code>.

💡 Hint

Think about how Cargo handles multiple versions of the same crate.

Cargo tries to unify dependencies to a single version. If foo and bar require incompatible versions of baz, Cargo cannot resolve the conflict, causing a build failure.

📝 Syntax

advanced

Which Cargo.toml snippet correctly specifies a git dependency?

You want to depend on a crate from a Git repository instead of crates.io. Which snippet is correct?

A

[dependencies]
mycrate = { git = "https://github.com/user/mycrate.git", branch = "main" }

B

[dependencies]
mycrate = git: "https://github.com/user/mycrate.git", branch = "main"

C

[dependencies]
mycrate = { url = "https://github.com/user/mycrate.git", branch = "main" }

D

[dependencies]
mycrate = { git = "https://github.com/user/mycrate.git" branch = "main" }

💡 Hint

Check the correct key name and syntax for specifying git dependencies in Cargo.toml.

The correct syntax uses git as the key inside braces with commas separating fields. Option A is correct. Option A uses invalid syntax, C uses wrong key url, and A misses a comma.

🚀 Application

expert

How many dependencies will Cargo build with this workspace setup?

Given a Cargo workspace with two crates:

[workspace]
members = ["crate_a", "crate_b"]

# crate_a/Cargo.toml
[dependencies]
serde = "1.0"

# crate_b/Cargo.toml
[dependencies]
serde = "1.0"
regex = "1.5"

How many unique dependencies will Cargo compile for the entire workspace?

A 1

B 4

C 3

D 2

💡 Hint

Consider shared dependencies and unique dependencies across workspace members.

Both crates depend on serde "1.0" (compatible, so compiled once). crate_b also depends on regex. Thus, two unique dependencies: serde and regex. Workspace members are packages, not dependencies.

Practice

1. What is the main purpose of the Cargo.toml file in a Rust project?

easy

A. To store the project's binary executable

B. To write the main Rust code logic

C. To compile the Rust project manually

D. To list and manage the project's dependencies

Solution

1. Step 1: Understand Cargo.toml role

   The Cargo.toml file is used to declare dependencies and project metadata.

2. Step 2: Differentiate from other files

   The Rust code logic is in src/main.rs, not Cargo.toml. Compilation is done by Cargo commands, not by the file itself.

3. Final Answer:

   To list and manage the project's dependencies -> Option D

4. Quick Check:

   Cargo.toml manages dependencies [OK]

Hint: Remember: Cargo.toml lists dependencies, not code [OK]

Common Mistakes:

• Confusing Cargo.toml with source code files
• Thinking Cargo.toml compiles code
• Assuming Cargo.toml stores executables

2. Which of the following is the correct syntax to add the dependency serde version 1.0 in Cargo.toml?

easy

A. serde = "1.0"

B. serde: "1.0"

C. "serde" = 1.0

D. serde => "1.0"

Solution

1. Step 1: Recall Cargo.toml dependency syntax

   Dependencies are listed as name = "version" pairs in Cargo.toml.

2. Step 2: Match correct syntax

   serde = "1.0" matches the correct syntax: serde = "1.0". Other options use invalid symbols.

3. Final Answer:

   serde = "1.0" -> Option A

4. Quick Check:

   Dependency syntax = name = "version" [OK]

Hint: Use equals and quotes for version in Cargo.toml [OK]

Common Mistakes:

• Using colon or arrow instead of equals
• Omitting quotes around version
• Putting quotes around dependency name incorrectly

3. Given this Cargo.toml snippet:

[dependencies]
regex = "1.5"

What happens when you run cargo build for the first time?

medium

A. Cargo throws an error because regex is not installed manually

B. Cargo ignores the regex crate and builds only your code

C. Cargo downloads and compiles the regex crate version 1.5

D. Cargo compiles your code but skips dependencies

Solution

1. Step 1: Understand Cargo build behavior

   When building, Cargo checks dependencies listed in Cargo.toml and downloads missing ones.

2. Step 2: Apply to regex dependency

   Since regex 1.5 is listed, Cargo downloads and compiles it automatically on first build.

3. Final Answer:

   Cargo downloads and compiles the regex crate version 1.5 -> Option C

4. Quick Check:

   cargo build downloads dependencies [OK]

Hint: cargo build auto-downloads missing dependencies [OK]

Common Mistakes:

• Thinking dependencies must be installed manually
• Assuming cargo build ignores dependencies
• Expecting errors if dependencies are new

4. You added a dependency in Cargo.toml but get an error: package not found when running cargo build. What is the likely cause?

medium

A. The dependency name is misspelled or does not exist on crates.io

B. You forgot to write cargo update before building

C. Cargo.toml must be renamed to Cargo.lock

D. Rust compiler version is too old

Solution

1. Step 1: Analyze error meaning

   "Package not found" means Cargo cannot find the named crate in the registry.

2. Step 2: Identify common causes

   This usually happens if the dependency name is misspelled or the crate does not exist on crates.io.

3. Final Answer:

   The dependency name is misspelled or does not exist on crates.io -> Option A

4. Quick Check:

   Package not found = wrong dependency name [OK]

Hint: Check spelling of dependency names carefully [OK]

Common Mistakes:

• Thinking cargo update fixes missing package errors
• Renaming Cargo.toml to Cargo.lock
• Blaming Rust version without checking dependency name

5. You want to use two different versions of the same crate log in your project: version 0.4 for your code and version 0.3 for a dependency. How can Cargo handle this situation?

hard

A. Cargo will fail to build due to version conflict

B. Cargo allows multiple versions of the same crate to coexist in the dependency tree

C. You must manually merge the versions into one in Cargo.toml

D. Cargo ignores the older version and uses only the newest

Solution

1. Step 1: Understand Cargo's version handling

   Cargo supports multiple versions of the same crate in the dependency tree to avoid conflicts.

2. Step 2: Apply to example

   Your code can use log 0.4 while a dependency uses log 0.3; Cargo compiles both separately.

3. Final Answer:

   Cargo allows multiple versions of the same crate to coexist in the dependency tree -> Option B

4. Quick Check:

   Cargo supports multiple crate versions [OK]

Hint: Cargo handles multiple crate versions automatically [OK]

Common Mistakes:

• Assuming Cargo fails on version conflicts
• Trying to merge versions manually
• Thinking Cargo ignores older versions