Defer execution order in Go - Time & Space Complexity

Time Complexity: Defer execution order

O(n)

Understanding Time Complexity

When using defer in Go, it's important to know how the order of deferred calls affects program steps.

We want to see how the number of deferred calls impacts the total work done when the function ends.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

func example(n int) {
    for i := 0; i < n; i++ {
        defer func(x int) {
            println(x)
        }(i)
    }
}

This code defers printing numbers from 0 to n-1, storing each deferred call during the loop.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Loop runs n times, each time adding one deferred function call.
• How many times: Exactly n deferred calls are stacked.

How Execution Grows With Input

Each loop adds one deferred call, and at the end, all deferred calls run in reverse order.

Input Size (n)	Approx. Operations
10	10 deferred calls added and then 10 executed
100	100 deferred calls added and then 100 executed
1000	1000 deferred calls added and then 1000 executed

Pattern observation: The total work grows linearly with n because each deferred call is stored and later executed once.

Final Time Complexity

Time Complexity: O(n)

This means the total steps grow in a straight line as the number of deferred calls increases.

Common Mistake

[X] Wrong: "Deferred calls run immediately or only once at the end without extra cost."

[OK] Correct: Deferred calls are stacked during execution and all run later, so the total work includes both stacking and running each deferred call.

Interview Connect

Understanding how defer stacks calls and affects execution helps you reason about function cleanup and resource management in real programs.

Self-Check

"What if we replaced defer with immediate function calls inside the loop? How would the time complexity change?"

Practice

1. What happens when multiple defer statements are used in a Go function?

easy

A. Deferred calls execute in last-in, first-out order when the function returns.

B. Deferred calls execute immediately when encountered.

C. Deferred calls execute in the order they appear in the code.

D. Deferred calls never execute automatically.

Solution

1. Step 1: Understand defer behavior

   In Go, deferred functions are postponed until the surrounding function returns.

2. Step 2: Execution order of deferred calls

   Deferred calls run in reverse order of their appearance, like a stack (last-in, first-out).

3. Final Answer:

   Deferred calls execute in last-in, first-out order when the function returns. -> Option A

4. Quick Check:

   Defer order = last-in, first-out [OK]

Hint: Remember: defer calls run backwards at function end [OK]

Common Mistakes:

• Thinking defer calls run immediately
• Assuming defer calls run in code order
• Believing defer calls never run

2. Which of the following is the correct syntax to defer a function call in Go?

easy

A. defer() fmt.Println("Hello")

B. defer := fmt.Println("Hello")

C. defer fmt.Println("Hello")

D. defer call fmt.Println("Hello")

Solution

1. Step 1: Recall defer syntax

   The keyword defer is followed directly by the function call without assignment or parentheses around defer.

2. Step 2: Identify correct syntax

   defer fmt.Println("Hello") correctly uses defer fmt.Println("Hello"). Other options misuse defer syntax.

3. Final Answer:

   defer fmt.Println("Hello") -> Option C

4. Quick Check:

   defer + function call = correct syntax [OK]

Hint: Use 'defer' directly before function call without extra symbols [OK]

Common Mistakes:

• Adding := after defer
• Using parentheses after defer keyword
• Writing extra words like 'call' after defer

3. What is the output of this Go program?

package main
import "fmt"
func main() {
    defer fmt.Println("First")
    defer fmt.Println("Second")
    fmt.Println("Third")
}

medium

A. Third
First
Second

B. Third
Second
First

C. First
Second
Third

D. Second
First
Third

Solution

1. Step 1: Identify immediate and deferred prints

   "Third" is printed immediately. The two deferred prints run after main ends.

2. Step 2: Determine deferred call order

   Deferred calls run last-in, first-out, so "Second" prints before "First".

3. Final Answer:

   Third Second First -> Option B

4. Quick Check:

   Immediate then deferred reverse order = Third, Second, First [OK]

Hint: Immediate prints first; deferred prints run backward after [OK]

Common Mistakes:

• Assuming deferred prints run in code order
• Thinking deferred prints run before immediate prints
• Confusing the order of deferred calls

4. Consider this Go code snippet:

func example() {
    defer fmt.Println("A")
    defer fmt.Println("B")
    defer fmt.Println("C")
    fmt.Println("D")
}

If the output is not as expected, what is the likely mistake?

medium

A. The function does not call fmt.Println("D") before defers.

B. The deferred calls are not in reverse order.

C. The deferred calls are missing parentheses.

D. The deferred calls execute immediately, not at function end.

Solution

1. Step 1: Understand expected output order

   "D" should print first immediately, then deferred calls print "C", "B", "A" in reverse order.

2. Step 2: Identify cause of unexpected output

   If "D" is missing or not printed before defers, output order changes unexpectedly.

3. Final Answer:

   The function does not call fmt.Println("D") before defers. -> Option A

4. Quick Check:

   Immediate prints must run before deferred calls [OK]

Hint: Ensure immediate prints run before deferred calls [OK]

Common Mistakes:

• Expecting deferred calls to run in code order
• Forgetting to call immediate print before defers
• Misunderstanding when deferred calls execute

5. You want to open three files in a Go function and ensure all are closed properly using defer. Which code snippet correctly closes the files in the right order?

hard

A. file1.Close()
file2.Close()
file3.Close()

B. defer file3.Close()
defer file2.Close()
defer file1.Close()

C. defer Close(file1)
defer Close(file2)
defer Close(file3)

D. defer file1.Close()
defer file2.Close()
defer file3.Close()

Solution

1. Step 1: Understand defer closing order

   Deferred calls run last-in, first-out, so the last deferred closes first.

2. Step 2: Apply to file closing

   Deferring file1.Close() first, then file2.Close(), then file3.Close() means file3 closes first, then file2, then file1, matching open order reversed.

3. Final Answer:

   defer file1.Close() defer file2.Close() defer file3.Close() -> Option D

4. Quick Check:

   Defer in open order closes files in reverse [OK]

Hint: Defer closes in reverse order of defer statements [OK]

Common Mistakes:

• Deferring closes in reverse order of opening
• Calling Close() immediately without defer
• Using incorrect function calls for closing