Why variables are needed in Go - Performance Analysis

Time Complexity: Why variables are needed

O(1)

Understanding Time Complexity

We want to see how using variables affects the steps a program takes.

How does the program's work change when it stores and reuses values?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

package main

import "fmt"

func main() {
    a := 5
    b := 10
    c := a + b
    fmt.Println(c)
}

This code stores numbers in variables and adds them together once.

Identify Repeating Operations

Look for repeated actions like loops or repeated calculations.

• Primary operation: Single addition of two variables.
• How many times: Exactly once, no loops or repeats.

How Execution Grows With Input

The program does the same small number of steps no matter what.

Input Size (n)	Approx. Operations
10	3 (2 assignments + 1 addition)
100	3 (same steps)
1000	3 (still the same)

Pattern observation: The number of steps stays the same no matter how big the numbers are.

Final Time Complexity

Time Complexity: O(1)

This means the program takes a fixed amount of time, no matter the input size.

Common Mistake

[X] Wrong: "Using variables makes the program slower because it stores values."

[OK] Correct: Storing values in variables is very fast and helps avoid repeating work, so it does not slow down the program.

Interview Connect

Understanding how variables affect program steps shows you know how programs manage data efficiently.

Self-Check

"What if we replaced variables with repeated calculations? How would the time complexity change?"