Function call flow in Rust

Introduction

Functions help organize code by breaking tasks into small steps. Understanding how function calls flow helps you follow what the program does step-by-step.

When you want to reuse a piece of code multiple times.

When you want to break a big problem into smaller, easier parts.

When you want to make your code easier to read and understand.

When you want to test parts of your program separately.

When you want to pass information between different parts of your program.

Syntax

Rust

fn function_name(parameters) {
    // code to run
}

function_name(arguments);

Functions start with fn, followed by the name and parentheses.

You call a function by writing its name and giving any needed values inside parentheses.

Examples

This function prints a greeting. Calling greet() runs the code inside.

Rust

fn greet() {
    println!("Hello!");
}

greet();

This function adds two numbers and returns the result. We call it with 3 and 4, then print the sum.

Rust

fn add(a: i32, b: i32) -> i32 {
    a + b
}

let sum = add(3, 4);
println!("Sum is {}", sum);

Sample Program

This program shows how functions call each other. main calls start, which calls middle, which calls end. The print statements show the order of calls and returns.

Rust

fn start() {
    println!("Start function called");
    middle();
    println!("Back to start function");
}

fn middle() {
    println!("Middle function called");
    end();
}

fn end() {
    println!("End function called");
}

fn main() {
    println!("Program begins");
    start();
    println!("Program ends");
}

Important Notes

When a function calls another, the program waits for the called function to finish before continuing.

Functions can call themselves (recursion), but be careful to avoid infinite loops.

Use clear function names to make the flow easier to understand.

Summary

Functions break code into small, reusable parts.

Calling a function runs its code and then returns to where it was called.

Understanding call flow helps you follow what your program does step-by-step.

Practice

1. What happens when a function is called in Rust?

easy

A. The program runs the function's code and then returns to the call point.

B. The program skips the function's code and continues after the call.

C. The function code runs only if called twice.

D. The program stops running after the function call.

Solution

1. Step 1: Understand function call behavior

   When a function is called, the program jumps to the function's code and executes it.

2. Step 2: Return to the call point

   After the function finishes, the program returns to the line after the call and continues running.

3. Final Answer:

   The program runs the function's code and then returns to the call point. -> Option A

4. Quick Check:

   Function call flow = run code then return [OK]

Hint: Function calls run code then return to caller [OK]

Common Mistakes:

• Thinking function code is skipped
• Believing program stops after call
• Assuming function runs only if called twice

2. Which of these is the correct way to call a function named greet in Rust?

easy

A. call greet;

B. greet();

C. greet[];

D. function greet();

Solution

1. Step 1: Recall Rust function call syntax

   Functions are called by writing their name followed by parentheses, even if no arguments are passed.

2. Step 2: Match the correct syntax

   Only greet(); matches this pattern correctly.

3. Final Answer:

   greet(); -> Option B

4. Quick Check:

   Function call syntax = name + () [OK]

Hint: Use functionName() to call functions in Rust [OK]

Common Mistakes:

• Omitting parentheses when calling functions
• Using brackets [] instead of parentheses
• Using keywords like 'call' or 'function' incorrectly

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

fn add_one(x: i32) -> i32 {
    x + 1
}

fn main() {
    let result = add_one(5);
    println!("{}", result);
}

medium

A. 5

B. Error: missing semicolon

C. 6

D. 0

Solution

1. Step 1: Understand the function behavior

   The function add_one takes an integer and returns that integer plus one.

2. Step 2: Trace the function call and output

   Calling add_one(5) returns 6, which is printed by println!.

3. Final Answer:

   6 -> Option C

4. Quick Check:

   5 + 1 = 6 [OK]

Hint: Follow function return values to find output [OK]

Common Mistakes:

• Confusing input and output values
• Thinking semicolon causes error here
• Assuming function prints instead of returns

4. Identify the error in this Rust code snippet:

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

fn main() {
    let result = multiply(4);
    println!("{}", result);
}

medium

A. Function multiply is missing a return statement.

B. Variable result is not declared.

C. println! macro is used incorrectly.

D. multiply is called with wrong number of arguments.

Solution

1. Step 1: Check function definition parameters

   The function multiply requires two arguments: x and y.

2. Step 2: Check function call arguments

   The call multiply(4) provides only one argument, causing an error.

3. Final Answer:

   multiply is called with wrong number of arguments. -> Option D

4. Quick Check:

   Function call args must match definition [OK]

Hint: Match function call arguments to definition [OK]

Common Mistakes:

• Ignoring argument count mismatch
• Thinking missing return causes error here
• Assuming println! usage is wrong

5. Given these functions:

fn first() {
    println!("Start");
    second();
    println!("End");
}

fn second() {
    println!("Middle");
}

fn main() {
    first();
}

What is the order of printed lines when main runs?

hard

A. Start\nMiddle\nEnd

B. Middle\nStart\nEnd

C. Start\nEnd\nMiddle

D. End\nMiddle\nStart

Solution

1. Step 1: Trace the call flow from main

   Main calls first(), which prints "Start" then calls second().

2. Step 2: Follow nested function calls

   second() prints "Middle" and returns. Then first() prints "End".

3. Final Answer:

   Start\nMiddle\nEnd -> Option A

4. Quick Check:

   Call flow order = Start, Middle, End [OK]

Hint: Follow calls step-by-step to find print order [OK]

Common Mistakes:

• Ignoring nested function call order
• Assuming prints happen after all calls
• Mixing up print sequence