Module visibility in Rust - Time & Space Complexity

Time Complexity: Module visibility

O(n)

Understanding Time Complexity

When working with module visibility in Rust, it's important to understand how access to code parts affects program behavior.

We want to see how the visibility rules impact the number of operations or checks done as the code grows.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

mod outer {
    pub mod inner {
        pub fn greet() {
            println!("Hello from inner module!");
        }
    }
}

fn main() {
    outer::inner::greet();
}
    

This code defines nested modules with public visibility and calls a function from the inner module.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: There are no loops or recursion here; the main operation is a single function call through module paths.
• How many times: The function is called once in this example.

How Execution Grows With Input

Explain the growth pattern intuitively.

Input Size (n)	Approx. Operations
10	10 function calls
100	100 function calls
1000	1000 function calls

Pattern observation: The number of operations grows linearly with the number of function calls, regardless of module visibility.

Final Time Complexity

Time Complexity: O(n)

This means the time to run grows directly with how many times you call functions through modules.

Common Mistake

[X] Wrong: "Making modules public slows down the program a lot because of extra checks."

[OK] Correct: Visibility controls are checked at compile time, so they don't add extra work when the program runs.

Interview Connect

Understanding how module visibility affects program structure helps you write clear and maintainable code, a skill valued in many coding tasks.

Self-Check

"What if we changed the inner module's visibility from public to private? How would the time complexity change when calling its functions?"

Practice

1. What does the pub keyword do in Rust module visibility?

easy

A. Makes a function or item accessible outside its module

B. Makes a function private to its module

C. Deletes the function from the module

D. Renames the function for external use

Solution

1. Step 1: Understand the role of pub

   The pub keyword in Rust is used to make functions, structs, or other items accessible from outside the module they are defined in.

2. Step 2: Contrast with default visibility

   By default, items are private and cannot be accessed outside their module unless marked with pub.

3. Final Answer:

   Makes a function or item accessible outside its module -> Option A

4. Quick Check:

   pub = public access [OK]

Hint: Remember: pub means public, so others can use it [OK]

Common Mistakes:

• Thinking pub hides the item
• Confusing pub with renaming
• Assuming pub deletes the item

2. Which of the following is the correct way to make a struct public in Rust?

easy

A. struct MyStruct { pub field: i32 }

B. struct pub MyStruct { field: i32 }

C. pub struct MyStruct { field: i32 }

D. struct MyStruct pub { field: i32 }

Solution

1. Step 1: Recall correct syntax for public structs

   In Rust, to make a struct public, the pub keyword must come before the struct keyword.

2. Step 2: Check placements of pub

   pub struct MyStruct { field: i32 } correctly places pub before struct. Placing pub inside the braces (on field), writing struct pub MyStruct, or struct MyStruct pub {} are incorrect.

3. Final Answer:

   pub struct MyStruct { field: i32 } -> Option C

4. Quick Check:

   pub struct is correct syntax [OK]

Hint: pub goes before struct, not inside or after [OK]

Common Mistakes:

• Placing pub inside struct braces
• Putting pub after struct name
• Writing pub in the wrong order

3. Given the code:

pub mod outer {
    pub mod inner {
        pub fn greet() { println!("Hello!"); }
    }
}

fn main() {
    outer::inner::greet();
}

What will be the output when this code runs?

medium

A. No output

B. Error: greet is private

C. Error: inner module is private

D. Hello!

Solution

1. Step 1: Check visibility of modules and function

   The outer module is public, containing pub mod inner with pub fn greet(), making them all accessible from main.

2. Step 2: Confirm function call and output

   The call outer::inner::greet() is valid and will print "Hello!" to the console.

3. Final Answer:

   Hello! -> Option D

4. Quick Check:

   pub modules and functions allow access [OK]

Hint: pub on modules and functions means accessible outside [OK]

Common Mistakes:

• Overlooking that the outer module needs pub
• Thinking greet is private by default
• Ignoring nested module visibility

4. What is wrong with this Rust code?

mod my_mod {
    fn secret() {
        println!("Secret function");
    }
}

fn main() {
    my_mod::secret();
}

medium

A. secret function is private and cannot be called from main

B. Missing semicolon after println!

C. Module my_mod is not declared public

D. Function secret must have pub keyword inside main

Solution

1. Step 1: Check function visibility

   The function secret is not marked pub, so it is private to my_mod.

2. Step 2: Understand call from main

   Since main is outside my_mod, it cannot call a private function, causing a compile error.

3. Final Answer:

   secret function is private and cannot be called from main -> Option A

4. Quick Check:

   Private functions can't be accessed outside module [OK]

Hint: Private functions can't be called outside their module [OK]

Common Mistakes:

• Thinking module must be pub to call function
• Assuming missing semicolon causes error
• Believing pub inside main is needed

5. You have a private struct Config inside a module, but want to allow other modules to create instances with limited access to its fields. Which visibility setup is correct?

hard

A. Make struct private and fields public

B. Make struct pub but keep fields private

C. Make both struct and fields private

D. Keep struct private and make fields pub

Solution

1. Step 1: Understand struct and field visibility

   Making the struct pub allows other modules to create instances, but keeping fields private restricts direct access to internal data.

2. Step 2: Evaluate other approaches

   Keeping the struct private (with or without pub fields) prevents other modules from constructing instances. Making everything private blocks access entirely.

3. Final Answer:

   Make struct pub but keep fields private -> Option B

4. Quick Check:

   pub struct + private fields = controlled access [OK]

Hint: pub struct with private fields controls access well [OK]

Common Mistakes:

• Making fields pub but struct private (no instance creation)
• Making everything private (no access)
• Exposing fields unintentionally