Return values in Rust - Time & Space Complexity

Time Complexity: Return values

O(n)

Understanding Time Complexity

We want to understand how the time it takes to get a return value changes as the input grows.

How does the program's work increase when returning values from functions?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

fn sum_array(arr: &[i32]) -> i32 {
    let mut total = 0;
    for &num in arr {
        total += num;
    }
    total
}

This function adds all numbers in an array and returns the total sum.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through each element in the array.
• How many times: Once for every element in the input array.

How Execution Grows With Input

As the array gets bigger, the function does more additions, one for each number.

Input Size (n)	Approx. Operations
10	10 additions
100	100 additions
1000	1000 additions

Pattern observation: The work grows directly with the number of items; double the items, double the work.

Final Time Complexity

Time Complexity: O(n)

This means the time to get the return value grows in a straight line with the input size.

Common Mistake

[X] Wrong: "Returning a value is always instant and does not depend on input size."

[OK] Correct: Sometimes returning a value means doing work first, like adding all numbers, so time depends on input size.

Interview Connect

Understanding how return values affect time helps you explain your code clearly and shows you know how programs grow with input.

Self-Check

"What if the function returned the maximum number instead of the sum? How would the time complexity change?"

Practice

1. What does the return value of a Rust function represent?

easy

A. The type of variables inside the function

B. The name of the function

C. The number of lines in the function

D. The result the function sends back to the caller

Solution

1. Step 1: Understand function purpose

   A function processes data and often produces a result.

2. Step 2: Identify return value role

   The return value is the output sent back to where the function was called.

3. Final Answer:

   The result the function sends back to the caller -> Option D

4. Quick Check:

   Return value = function output [OK]

Hint: Return value is what function gives back [OK]

Common Mistakes:

• Confusing return value with function name
• Thinking return value is the number of lines
• Mixing return value with variable types

2. Which of the following is the correct way to declare a function in Rust that returns an i32 value?

easy

A. fn add() returns i32 { 5 + 3 }

B. fn add() -> i32 { 5 + 3 }

C. fn add() : i32 { 5 + 3 }

D. fn add() -> int { 5 + 3 }

Solution

1. Step 1: Check Rust return syntax

   Rust uses -> Type to specify return type after function parentheses.

2. Step 2: Validate options

   fn add() -> i32 { 5 + 3 } uses -> i32 correctly; others use invalid syntax or wrong type name.

3. Final Answer:

   fn add() -> i32 { 5 + 3 } -> Option B

4. Quick Check:

   Return type syntax = -> Type [OK]

Hint: Use -> Type after () to declare return type [OK]

Common Mistakes:

• Using colon : instead of -> for return type
• Writing 'returns' keyword incorrectly
• Using 'int' instead of 'i32' in Rust

3. What is the output of this Rust code?

fn multiply(x: i32, y: i32) -> i32 {
    x * y
}

fn main() {
    println!("{}", multiply(4, 5));
}

medium

A. 20

B. 45

C. 9

D. Compilation error

Solution

1. Step 1: Understand function multiply

   It returns the product of x and y without explicit return keyword.

2. Step 2: Calculate multiply(4, 5)

   4 * 5 = 20, so the function returns 20.

3. Final Answer:

   20 -> Option A

4. Quick Check:

   4 * 5 = 20 [OK]

Hint: Last expression is returned automatically [OK]

Common Mistakes:

• Expecting explicit return keyword
• Confusing multiplication with addition
• Thinking code causes error due to missing return

4. Identify the error in this Rust function that is supposed to return an i32:

fn get_number() -> i32 {
    let x = 10;
    return;
}

medium

A. Variable x is unused

B. Function should not have a return type

C. Missing return value after return keyword

D. Function should use println! instead of return

Solution

1. Step 1: Check return statement

   The function declares return type i32 but uses return; without value.

2. Step 2: Understand Rust return rules

   Functions with return type must return a value of that type; missing value causes error.

3. Final Answer:

   Missing return value after return keyword -> Option C

4. Quick Check:

   Return type requires value [OK]

Hint: Return type needs a value after return [OK]

Common Mistakes:

• Omitting return value when return type is specified
• Ignoring unused variable warnings
• Confusing return with print statements

5. Given this Rust function, what will be the output?

fn check_value(x: i32) -> bool {
    if x > 0 {
        true
    } else {
        false
    }
}

fn main() {
    println!("{}", check_value(-3));
}

hard

A. false

B. Compilation error

C. 0

D. true

Solution

1. Step 1: Analyze function check_value

   Returns true if x > 0, else false.

2. Step 2: Evaluate check_value(-3)

   -3 is not greater than 0, so function returns false.

3. Final Answer:

   false -> Option A

4. Quick Check:

   x > 0 ? true : false = false [OK]

Hint: If condition returns last expression automatically [OK]

Common Mistakes:

• Assuming negative numbers return true
• Expecting numeric output instead of bool
• Thinking missing return causes error