Scope of variables in Rust

Introduction

Scope tells us where a variable can be used in the code. It helps keep things organized and avoids mistakes.

When you want to use a variable only inside a small part of your program.

When you want to avoid changing a variable by mistake in other parts of the code.

When you want to reuse the same variable name in different parts without conflict.

When you want to understand where a variable is created and where it stops existing.

Syntax

Rust

fn main() {
    let x = 5; // x is valid from here
    {
        let y = 10; // y is valid only inside this block
        println!("x = {}, y = {}", x, y);
    } // y is no longer valid here
    println!("x = {}", x);
    // println!("y = {}", y); // This would cause an error
}

Variables declared inside curly braces {} are only usable inside those braces.

Variables declared outside are usable inside inner blocks too.

Examples

Variable b is only inside the inner block. Outside, it is not known.

Rust

fn main() {
    let a = 1;
    {
        let b = 2;
        println!("a = {}, b = {}", a, b);
    }
    // println!("b = {}", b); // Error: b not in scope here
}

Variable x is declared in main and can be used anywhere inside main.

Rust

fn main() {
    let x = 10;
    println!("x = {}", x);
}

You can declare a new variable with the same name inside a block. It hides the outer one temporarily.

Rust

fn main() {
    let x = 5;
    {
        let x = 10; // shadows outer x
        println!("inner x = {}", x);
    }
    println!("outer x = {}", x);
}

Sample Program

This program shows how a variable inside a block can hide the same variable outside. The outer variable keeps its value after the block.

Rust

fn main() {
    let number = 7;
    println!("Outside block: number = {}", number);
    {
        let number = 42; // shadows outer number
        println!("Inside block: number = {}", number);
    }
    println!("After block: number = {}", number);
}

Important Notes

Shadowing lets you reuse variable names safely inside smaller scopes.

Trying to use a variable outside its scope causes a compile error.

Summary

Scope defines where a variable can be used.

Variables inside blocks are only valid inside those blocks.

Shadowing allows temporary replacement of a variable inside a smaller scope.

Practice

1. What does the scope of a variable in Rust determine?

easy

A. Where the variable can be accessed or used

B. The type of the variable

C. The value stored in the variable

D. The memory size of the variable

Solution

1. Step 1: Understand the meaning of scope

   Scope means the part of the code where a variable is valid and can be used.

2. Step 2: Identify what scope controls

   Scope controls access to the variable, not its type, value, or memory size.

3. Final Answer:

   Where the variable can be accessed or used -> Option A

4. Quick Check:

   Scope = access area [OK]

Hint: Scope means where you can use the variable [OK]

Common Mistakes:

• Confusing scope with variable type
• Thinking scope controls variable value
• Mixing scope with memory size

2. Which of the following is the correct way to declare a variable inside a block in Rust?

easy

A. var x = 5;

B. let x = 5;

C. int x = 5;

D. declare x = 5;

Solution

1. Step 1: Recall Rust variable declaration syntax

   Rust uses let keyword to declare variables.

2. Step 2: Check each option

   Only let x = 5; is valid Rust syntax; others are from other languages or invalid.

3. Final Answer:

   let x = 5; -> Option B

4. Quick Check:

   Rust variables start with let [OK]

Hint: Rust variables start with let keyword [OK]

Common Mistakes:

• Using var instead of let
• Using type declarations like int
• Using declare keyword

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

fn main() {
    let x = 10;
    {
        let x = 20;
        println!("{}", x);
    }
    println!("{}", x);
}

medium

A. 10\n10

B. 20\n20

C. 10\n20

D. 20\n10

Solution

1. Step 1: Identify variable shadowing inside inner block

   Inside the inner block, x is redefined as 20, shadowing outer x.

2. Step 2: Trace the print statements

   First print shows inner x = 20; second print shows outer x = 10.

3. Final Answer:

   20 10 -> Option D

4. Quick Check:

   Inner shadow = 20, outer original = 10 [OK]

Hint: Inner block shadows outer variable [OK]

Common Mistakes:

• Ignoring shadowing and printing outer value twice
• Assuming inner variable changes outer variable
• Confusing print order

4. Identify the error in this Rust code snippet:

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

medium

A. Variable y is used outside its scope

B. Missing semicolon after let y = 5

C. println! macro is misspelled

D. No error, code runs fine

Solution

1. Step 1: Check where y is declared and used

   Variable y is declared inside inner block and goes out of scope after block ends.

2. Step 2: Analyze usage of y outside block

   Using y in println! outside block causes error because y is not visible there.

3. Final Answer:

   Variable y is used outside its scope -> Option A

4. Quick Check:

   Use inside scope only [OK]

Hint: Variables vanish outside their block scope [OK]

Common Mistakes:

• Thinking semicolon is missing
• Assuming println! is wrong
• Ignoring variable scope rules

5. Consider this Rust code:

fn main() {
    let mut count = 0;
    for i in 0..3 {
        let count = count + i;
        println!("{}", count);
    }
    println!("Final count: {}", count);
}

What will be the output and why?

hard

A. 0\n1\n2\nFinal count: 6

B. 0\n1\n2\nFinal count: 2

C. 0\n1\n2\nFinal count: 0

D. Compilation error due to variable shadowing

Solution

1. Step 1: Understand variable shadowing inside the loop

   Inside the loop, count is shadowed by a new variable count equal to outer count plus i. Outer count remains unchanged.

2. Step 2: Trace loop iterations and prints

   Iterations: i=0 -> inner count=0, print 0; i=1 -> inner count=1, print 1; i=2 -> inner count=2, print 2. Outer count stays 0.

3. Step 3: Final print shows outer count

   After loop, outer count is still 0, so prints "Final count: 0".

4. Final Answer:

   0 1 2 Final count: 0 -> Option C

5. Quick Check:

   Shadowing hides outer count, outer unchanged [OK]

Hint: Shadowing inside loop doesn't change outer variable [OK]

Common Mistakes:

• Assuming outer count changes inside loop
• Confusing shadowing with mutation
• Expecting sum accumulation in outer count