Why modules are used in Rust - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a module named math.

Rust

mod [1] {}

Drag options to blanks, or click blank then click option'

Afn

Bmain

Cmath

Duse

Attempts:

3 left

💡 Hint

Common Mistakes

Using fn instead of a module name.

Writing use instead of mod.

The keyword mod declares a module, and math is the module name here.

2fill in blank

medium

Complete the code to use a function add from the math module.

Rust

fn main() {
    let sum = math::[1](2, 3);
    println!("Sum: {}", sum);
}

Drag options to blanks, or click blank then click option'

Aadd

Bsubtract

Cmod

Dmain

Attempts:

3 left

💡 Hint

Common Mistakes

Using the module name as a function.

Calling a function that does not exist.

To call a function inside a module, use module_name::function_name. Here, add is the function.

3fill in blank

hard

Fix the error by completing the code to declare a public function add inside the math module.

Rust

mod math {
    pub fn [1](a: i32, b: i32) -> i32 {
        a + b
    }
}

Drag options to blanks, or click blank then click option'

Aadd

Bsum

Cmain

Dmod

Attempts:

3 left

💡 Hint

Common Mistakes

Not using pub to make the function accessible.

Using a different function name than called.

The function name must be add to match the usage. pub makes it accessible outside the module.

4fill in blank

hard

Fill both blanks to import the add function from the math module and use it.

Rust

use crate::math::[1];

fn main() {
    let result = [2](5, 7);
    println!("Result: {}", result);
}

Drag options to blanks, or click blank then click option'

Aadd

Bsubtract

Dmain

Attempts:

3 left

💡 Hint

Common Mistakes

Using different names for import and call.

Not importing the function before use.

We import add with use and then call it directly by name.

5fill in blank

hard

Fill all three blanks to create a module utils with a public function greet and call it in main.

Rust

mod [1] {
    pub fn [2]() {
        println!("Hello from utils!");
    }
}

fn main() {
    [3]();
}

Drag options to blanks, or click blank then click option'

Autils

Bgreet

Dmain

Attempts:

3 left

💡 Hint

Common Mistakes

Not making the function public.

Calling the function without the correct name.

The module is named utils, the function is greet, and we call greet() in main.

Practice

1. Why do Rust programmers use modules in their code?

easy

A. To organize code into smaller, manageable parts

B. To make the program run faster

C. To increase the size of the compiled file

D. To avoid writing comments

Solution

1. Step 1: Understand the purpose of modules

   Modules help break down code into smaller parts that are easier to manage and understand.

2. Step 2: Compare other options

   Options A, B, and D do not describe the main reason for using modules; they are unrelated to code organization.

3. Final Answer:

   To organize code into smaller, manageable parts -> Option A

4. Quick Check:

   Modules organize code = C [OK]

Hint: Modules help split code into parts for clarity [OK]

Common Mistakes:

• Thinking modules speed up the program
• Believing modules increase file size
• Confusing modules with comments

2. Which of the following is the correct way to declare a module named math in Rust?

easy

A. module math { }

B. mod math { }

C. package math { }

D. use math { }

Solution

1. Step 1: Recall Rust module syntax

   Rust uses the keyword mod to declare a module.

2. Step 2: Check other options

   Options B, C, and D use incorrect keywords not valid in Rust for modules.

3. Final Answer:

   mod math { } -> Option B

4. Quick Check:

   Use mod to declare modules = A [OK]

Hint: Use 'mod' keyword to declare modules in Rust [OK]

Common Mistakes:

• Using 'module' instead of 'mod'
• Confusing 'use' with module declaration
• Trying 'package' keyword like other languages

3. What will be the output of this Rust code?

mod greetings {
    pub fn hello() {
        println!("Hello from module!");
    }
}

fn main() {
    greetings::hello();
}

medium

A. Compilation error: module not found

B. Error: function hello is private

C. Hello from module!

D. No output

Solution

1. Step 1: Check function visibility

   The function hello is marked pub, so it is accessible outside the module.

2. Step 2: Understand function call

   The main function calls greetings::hello(), which prints the message.

3. Final Answer:

   Hello from module! -> Option C

4. Quick Check:

   Public function call prints message = D [OK]

Hint: Public functions in modules can be called outside [OK]

Common Mistakes:

• Forgetting to use 'pub' makes function private
• Assuming no output without checking visibility
• Thinking module must be imported separately

4. Identify the error in this Rust code using modules:

mod tools {
    fn hammer() {
        println!("Hammering");
    }
}

fn main() {
    tools::hammer();
}

medium

A. Function hammer is private and cannot be accessed outside the module

B. Module tools is not declared correctly

C. Missing semicolon after println!

D. Cannot call functions inside modules

Solution

1. Step 1: Check function visibility

   The function hammer is not marked pub, so it is private to the module.

2. Step 2: Understand access rules

   Trying to call tools::hammer() from main causes an error because the function is private.

3. Final Answer:

   Function hammer is private and cannot be accessed outside the module -> Option A

4. Quick Check:

   Private function access error = A [OK]

Hint: Mark functions 'pub' to access outside modules [OK]

Common Mistakes:

• Assuming all module functions are public by default
• Thinking module declaration is wrong
• Missing semicolon in println! (actually correct here)

5. You want to organize a Rust project with two modules: math and utils. The math module has a public function add that you want to use in utils. How should you structure the code to allow utils to call math::add?

hard

A. Make add private and call it directly from utils

B. Modules cannot call functions from each other

C. Define add inside utils instead of math

D. Declare both modules in the root, mark add as pub, and use use crate::math::add; inside utils

Solution

1. Step 1: Make function public

   The add function must be marked pub to be accessible outside math.

2. Step 2: Use 'use' to import function

   Inside utils, use use crate::math::add; to bring add into scope for calling.

3. Final Answer:

   Declare both modules in the root, mark add as pub, and use use crate::math::add; inside utils -> Option D

4. Quick Check:

   Public function + use import = B [OK]

Hint: Make functions pub and import with use to share between modules [OK]

Common Mistakes:

• Leaving function private and expecting access
• Trying to call private functions directly
• Thinking modules cannot share code