Stack vs heap mental model in C Sharp (C#) - Hands-On Comparison

Stack vs Heap Mental Model in C#

📖 Scenario: Imagine you are organizing your workspace. You have a small desk drawer for quick notes (stack) and a big filing cabinet for important documents (heap). You want to understand how C# stores simple data and objects in these two places.

🎯 Goal: You will create a simple C# program that shows how value types (stored on the stack) and reference types (stored on the heap) behave differently. You will see how changing one variable affects another depending on where the data is stored.

📋 What You'll Learn

Create a value type variable and assign it a number

Create a reference type variable (class instance) with a number property

Copy the value type variable to another variable

Copy the reference type variable to another variable

Change the copied variables and observe the effect on the originals

Print the results to show the difference between stack and heap behavior

💡 Why This Matters

🌍 Real World

Understanding stack and heap helps you write efficient programs and avoid bugs related to data changes.

💼 Career

Many programming jobs require knowledge of memory management and how data is stored and accessed.

1

Create a value type variable

Create an int variable called stackNumber and set it to 10.

C Sharp (C#)

# Create an int variable called stackNumber and set it to 10
// Your code here

Hint

Use int stackNumber = 10; to create the variable.

2

Create a reference type variable

Create a class called HeapNumber with a public int property called Value. Then create an instance called heapNumber and set its Value to 10.

C Sharp (C#)

int stackNumber = 10;
// Create class HeapNumber with public int Value property
// Create instance heapNumber and set Value to 10
// Your code here

Hint

Define the class with a public property, then create an object and set its property.

3

Copy variables and change copies

Create a new int variable called stackCopy and set it equal to stackNumber. Create a new HeapNumber variable called heapCopy and set it equal to heapNumber. Then change stackCopy to 20 and heapCopy.Value to 20.

C Sharp (C#)

int stackNumber = 10;

class HeapNumber
{
    public int Value { get; set; }
}

HeapNumber heapNumber = new HeapNumber();
heapNumber.Value = 10;

// Copy stackNumber to stackCopy
// Copy heapNumber to heapCopy
// Change stackCopy to 20
// Change heapCopy.Value to 20
// Your code here

Hint

Assign the variables and then change the copies as instructed.

4

Print the results

Print the values of stackNumber, stackCopy, heapNumber.Value, and heapCopy.Value using Console.WriteLine to show how stack and heap behave differently.

C Sharp (C#)

int stackNumber = 10;

class HeapNumber
{
    public int Value { get; set; }
}

HeapNumber heapNumber = new HeapNumber();
heapNumber.Value = 10;

int stackCopy = stackNumber;
HeapNumber heapCopy = heapNumber;

stackCopy = 20;
heapCopy.Value = 20;

// Print stackNumber, stackCopy, heapNumber.Value, heapCopy.Value
// Your code here

Hint

Use Console.WriteLine with string interpolation to print the variable values.

Practice

1. In C#, where are value types like int and bool typically stored during program execution?

easy

A. On the heap, because they are objects that need dynamic memory

B. In static memory, shared across all instances

C. In the CPU cache only, not in stack or heap

D. On the stack, because they are stored directly and accessed quickly

Solution

1. Step 1: Understand value type storage

   Value types like int and bool are stored on the stack because they hold data directly and have a short lifetime.

2. Step 2: Contrast with heap storage

   Heap stores objects (reference types), not simple value types, which makes stack the correct place for these.

3. Final Answer:

   On the stack, because they are stored directly and accessed quickly -> Option D

4. Quick Check:

   Value types = stack [OK]

Hint: Value types go on stack; objects go on heap [OK]

Common Mistakes:

• Thinking all data goes on heap
• Confusing value types with reference types
• Assuming stack is for objects only

2. Which of the following C# declarations correctly creates a reference type stored on the heap?

easy

A. string text = "hello";

B. double pi = 3.14;

C. bool flag = true;

D. int number = 5;

Solution

1. Step 1: Identify reference types

   In C#, string is a reference type stored on the heap, while int, bool, and double are value types stored on the stack.

2. Step 2: Match declaration to heap storage

   Only string text = "hello"; creates a reference type object on the heap.

3. Final Answer:

   string text = "hello"; -> Option A

4. Quick Check:

   Reference type = string [OK]

Hint: Strings are reference types stored on heap [OK]

Common Mistakes:

• Assuming all primitives are reference types
• Confusing string as value type
• Ignoring heap for object storage

3. Consider the following C# code:

class Person { public string Name; }
Person p1 = new Person();
p1.Name = "Alice";
Person p2 = p1;
p2.Name = "Bob";
Console.WriteLine(p1.Name);

What will be the output and why?

medium

A. "Bob" because p1 and p2 reference the same object on the heap

B. Compilation error due to missing constructor

C. "Alice" because p1 and p2 are separate objects on the heap

D. "Alice" because strings are immutable

Solution

1. Step 1: Understand reference assignment

   Both p1 and p2 point to the same Person object on the heap because p2 = p1; copies the reference.

2. Step 2: Trace the name change effect

   Changing p2.Name to "Bob" changes the same object that p1 references, so p1.Name is also "Bob".

3. Final Answer:

   "Bob" because p1 and p2 reference the same object on the heap -> Option A

4. Quick Check:

   Reference copy = shared object [OK]

Hint: Reference copy means both variables point to same heap object [OK]

Common Mistakes:

• Thinking p1 and p2 are independent copies
• Confusing value and reference assignment
• Ignoring that strings are immutable but object fields can change

4. Identify the error in this C# code snippet related to stack and heap usage:

int[] numbers;
numbers[0] = 10;
Console.WriteLine(numbers[0]);

medium

A. Array elements are stored on stack but accessed incorrectly

B. Array is not initialized before use, causing a runtime error

C. Syntax error: missing semicolon after array declaration

D. No error; code runs and prints 10

Solution

1. Step 1: Check array initialization

   The array numbers is declared but not initialized, so it points to null by default.

2. Step 2: Understand runtime behavior

   Accessing numbers[0] without initialization causes a NullReferenceException at runtime.

3. Final Answer:

   Array is not initialized before use, causing a runtime error -> Option B

4. Quick Check:

   Uninitialized reference = runtime error [OK]

Hint: Always initialize arrays before accessing elements [OK]

Common Mistakes:

• Assuming declaration allocates memory
• Confusing stack and heap for array storage
• Ignoring runtime null reference errors

5. You want to optimize a C# program that creates many small objects rapidly. Which approach best uses the stack and heap to improve performance?

hard

A. Avoid using the stack by allocating everything on the heap

B. Use only reference types to ensure all data is on the heap for consistency

C. Use value types (structs) for small data to store on stack and reduce heap allocations

D. Use global static variables to store all objects

Solution

1. Step 1: Understand stack vs heap performance

   The stack is faster for allocation and deallocation, so using value types (structs) reduces heap pressure.

2. Step 2: Apply optimization strategy

   Using structs for small data stores them on the stack, avoiding costly heap allocations and garbage collection.

3. Final Answer:

   Use value types (structs) for small data to store on stack and reduce heap allocations -> Option C

4. Quick Check:

   Value types on stack = better performance [OK]

Hint: Use structs for small data to leverage fast stack allocation [OK]

Common Mistakes:

• Thinking heap is always better for performance
• Ignoring garbage collection overhead
• Using static variables without reason