Using external crates in Rust - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a crate in Rust?

A crate is a package of Rust code. It can be a library or a binary. Crates help organize and share code.

beginner

How do you add an external crate to your Rust project?

You add the crate name and version to the [dependencies] section in the Cargo.toml file.

beginner

What command downloads and compiles external crates listed in Cargo.toml?

The command cargo build downloads and compiles all dependencies including external crates.

beginner

How do you use an external crate in your Rust code after adding it to Cargo.toml?

You add use crate_name::module; at the top of your Rust file to bring the crate's code into scope.

intermediate

What is the purpose of extern crate in Rust?

In modern Rust editions, extern crate is mostly optional. It was used to link external crates before the 2018 edition.

Where do you specify external crates for a Rust project?

A In the .rs source files using #include

B In the main.rs file

C In the rustc compiler flags

D In the Cargo.toml file under [dependencies]

External crates are listed in the Cargo.toml file under the [dependencies] section.

Which command downloads and compiles external crates?

A cargo build

B cargo run

C rustc main.rs

D cargo test

cargo build downloads and compiles all dependencies including external crates.

How do you bring an external crate into scope in your Rust code?

A import crate_name;

B #include <crate_name>

C use crate_name::module;

D extern crate crate_name;

You use the use keyword to bring external crate modules into scope.

Is extern crate still required in Rust 2021 edition?

A Yes, always required

B No, it is mostly optional now

C Only for standard library crates

D Only for crates from crates.io

extern crate is mostly optional in Rust 2018 and later editions.

What file manages dependencies in a Rust project?

A Cargo.toml

B main.rs

C lib.rs

D rustc.toml

Cargo.toml is the configuration file where dependencies are declared.

Explain the steps to add and use an external crate in a Rust project.

Think about where you declare, how you get it, and how you use it.

What is the role of Cargo in managing external crates?

Cargo is like the project helper for Rust.

Practice

1. What is the main purpose of using external crates in a Rust project?

easy

A. To make the code run faster automatically

B. To avoid writing any code at all

C. To add extra functionality without writing it yourself

D. To replace the Rust compiler

Solution

1. Step 1: Understand what external crates are

   External crates are packages of code others wrote that you can use in your project.

2. Step 2: Identify their purpose

   They help you add features without coding everything from scratch.

3. Final Answer:

   To add extra functionality without writing it yourself -> Option C

4. Quick Check:

   External crates = add features easily [OK]

Hint: External crates add features you don't code yourself [OK]

Common Mistakes:

• Thinking crates speed up code automatically
• Believing crates replace Rust compiler
• Assuming crates remove all coding

2. Which of the following is the correct way to add an external crate named rand to your Rust project?

easy

A. Add import rand; in main.rs

B. Write use rand; in Cargo.toml

C. Add extern crate rand; in Cargo.toml

D. Add rand = "0.8" under [dependencies] in Cargo.toml

Solution

1. Step 1: Know where to add crate versions

   Crate versions go under [dependencies] in Cargo.toml file.

2. Step 2: Identify correct syntax

   The correct syntax is rand = "0.8" under [dependencies].

3. Final Answer:

   Add rand = "0.8" under [dependencies] in Cargo.toml -> Option D

4. Quick Check:

   Cargo.toml dependencies = rand = "0.8" [OK]

Hint: Add crate and version under [dependencies] in Cargo.toml [OK]

Common Mistakes:

• Trying to use 'use' or 'import' in Cargo.toml
• Writing extern crate in Cargo.toml instead of code
• Adding crate info in main.rs instead of Cargo.toml

3. Given the following code and Cargo.toml setup, what will be the output? Cargo.toml snippet:

[dependencies]
regex = "1"

main.rs snippet:

use regex::Regex;

fn main() {
    let re = Regex::new(r"\d+").unwrap();
    let text = "abc123def";
    println!("{}", re.is_match(text));
}

medium

A. true

B. false

C. Compilation error

D. Runtime panic

Solution

1. Step 1: Understand what the regex checks

   The regex looks for one or more digits (\d+) in the text "abc123def".

2. Step 2: Check if the text contains digits

   The text contains "123", so the regex matches and returns true.

3. Final Answer:

   true -> Option A

4. Quick Check:

   Regex match found = true [OK]

Hint: Regex \d+ matches digits in string, so output true [OK]

Common Mistakes:

• Thinking regex returns false if digits exist
• Expecting compilation error due to crate usage
• Assuming unwrap causes panic here

4. What is wrong with this Rust code using the chrono crate? Cargo.toml:

[dependencies]
chrono = "0.4"

main.rs:

use chrono::DateTime;

fn main() {
    let now = DateTime::now();
    println!("{}", now);
}

medium

A. Missing extern crate chrono declaration

B. DateTime::now() does not exist; use Utc::now() instead

C. Cargo.toml version is incorrect

D. println! macro cannot print DateTime

Solution

1. Step 1: Check DateTime usage

   DateTime::now() is not a valid method; chrono uses Utc::now() to get current time.

2. Step 2: Identify correct method to get current time

   Use chrono::Utc::now() to get current DateTime.

3. Final Answer:

   DateTime::now() does not exist; use Utc::now() instead -> Option B

4. Quick Check:

   Use Utc::now() for current time [OK]

Hint: Use Utc::now(), not DateTime::now() for current time [OK]

Common Mistakes:

• Trying to call DateTime::now() directly
• Forgetting to import chrono::Utc
• Assuming extern crate needed in 2018 edition

5. You want to use the serde_json crate to convert a Rust struct into a JSON string. Which steps are needed to do this correctly?

hard

A. Add serde and serde_json to Cargo.toml, derive Serialize on struct, then call serde_json::to_string

B. Only add serde_json to Cargo.toml and call to_string on struct directly

C. Add serde_json to Cargo.toml and use println!("{}", struct) without Serialize

D. Add serde to Cargo.toml and call struct.to_json() method

Solution

1. Step 1: Add required crates in Cargo.toml

   You must add both serde and serde_json under [dependencies] to use serialization features.

2. Step 2: Derive Serialize trait on your struct

   To convert struct to JSON, it must implement Serialize, usually by adding #[derive(Serialize)].

3. Step 3: Use serde_json::to_string to convert struct

   Call serde_json::to_string(&your_struct) to get JSON string.

4. Final Answer:

   Add serde and serde_json to Cargo.toml, derive Serialize on struct, then call serde_json::to_string -> Option A

5. Quick Check:

   Serialize + serde_json::to_string = JSON string [OK]

Hint: Add serde + serde_json, derive Serialize, then use to_string [OK]

Common Mistakes:

• Forgetting to add serde crate
• Not deriving Serialize on struct
• Trying to call to_string directly on struct