Program stability concepts in Go - Time & Space Complexity

Time Complexity: Program stability concepts

O(n)

Understanding Time Complexity

Program stability means how well a program keeps working correctly as input size changes.

We want to know how the program's speed changes when it handles more data.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

func stableProcess(data []int) int {
    result := 0
    for _, value := range data {
        if value%2 == 0 {
            result += value
        }
    }
    return result
}
    

This code sums all even numbers in a list of integers.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through each item in the data list.
• How many times: Once for every item in the list.

How Execution Grows With Input

As the list gets bigger, the program checks more numbers one by one.

Input Size (n)	Approx. Operations
10	About 10 checks
100	About 100 checks
1000	About 1000 checks

Pattern observation: The work grows directly with the number of items.

Final Time Complexity

Time Complexity: O(n)

This means the time to finish grows in a straight line with the input size.

Common Mistake

[X] Wrong: "The program runs faster because it only adds even numbers."

[OK] Correct: The program still checks every number, so the time depends on the total list size, not just the even numbers.

Interview Connect

Understanding how a program's speed changes with input size shows you can write stable and predictable code.

Self-Check

"What if we changed the code to sum only numbers greater than 100? How would the time complexity change?"

Practice

1. What is the main purpose of using recover() in Go programs?

easy

A. To declare a new variable

B. To start a new goroutine

C. To catch a panic and prevent the program from crashing

D. To handle normal errors returned by functions

Solution

1. Step 1: Understand panic and recover

   Panic causes a program to stop running immediately unless recovered.

2. Step 2: Role of recover()

   Recover is used inside a deferred function to catch the panic and allow the program to continue.

3. Final Answer:

   To catch a panic and prevent the program from crashing -> Option C

4. Quick Check:

   recover() catches panic = C [OK]

Hint: recover() only works inside deferred functions [OK]

Common Mistakes:

• Thinking recover() handles normal errors
• Using recover() outside defer
• Confusing recover() with panic()

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 -> fmt.Println("Hello")

Solution

1. Step 1: Recall defer syntax

   In Go, defer is a keyword placed before a function call to delay its execution.

2. Step 2: Check each option

   Only defer fmt.Println("Hello") uses 'defer' correctly before the function call without extra symbols.

3. Final Answer:

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

4. Quick Check:

   defer + function call = D [OK]

Hint: defer must be followed directly by a function call [OK]

Common Mistakes:

• Adding '=' after defer
• Using ':' or '->' after defer
• Not calling a function after defer

3. What will be the output of this Go program?

package main
import "fmt"
func main() {
    defer func() {
        if r := recover(); r != nil {
            fmt.Println("Recovered from panic:", r)
        }
    }()
    fmt.Println("Start")
    panic("Something went wrong")
    fmt.Println("End")
}

medium

A. Start
panic: Something went wrong

B. Start
End
Recovered from panic: Something went wrong

C. Start
End

D. Start
Recovered from panic: Something went wrong

Solution

1. Step 1: Trace program execution

   "Start" is printed first. Then panic is called, which triggers the deferred function.

2. Step 2: Deferred function recovers panic

   The deferred anonymous function calls recover(), catches the panic, and prints the recovery message. Execution does not continue after panic call, so "End" is not printed.

3. Final Answer:

   Start Recovered from panic: Something went wrong -> Option D

4. Quick Check:

   panic caught by recover = A [OK]

Hint: Deferred recover runs on panic, then execution continues after panic [OK]

Common Mistakes:

• Thinking code after panic does not run
• Missing recover() inside defer
• Confusing panic message with normal print

4. Identify the error in this Go code that tries to recover from a panic:

package main
import "fmt"
func main() {
    if r := recover(); r != nil {
        fmt.Println("Recovered:", r)
    }
    panic("Oops")
}

medium

A. recover() must be called inside a deferred function

B. panic() must be called before recover()

C. recover() cannot be used with panic()

D. fmt.Println() cannot be used inside if statement

Solution

1. Step 1: Understand recover usage

   recover() only works if called inside a deferred function; here it is called directly in main.

2. Step 2: Analyze code flow

   Since recover() is not deferred, it cannot catch the panic, so the program will crash.

3. Final Answer:

   recover() must be called inside a deferred function -> Option A

4. Quick Check:

   recover inside defer = B [OK]

Hint: Always call recover() inside defer to catch panics [OK]

Common Mistakes:

• Calling recover() directly without defer
• Thinking recover() catches errors, not panics
• Placing panic before recover without defer

5. You want to write a stable Go program that logs a message when a panic occurs but continues running. Which code snippet correctly implements this behavior?

hard

A. func main() {
if r := recover(); r != nil {
fmt.Println("Panic caught:", r)
}
panic("Crash")
fmt.Println("Program continues")
}

B. func main() {
defer func() {
if r := recover(); r != nil {
fmt.Println("Panic caught:", r)
}
}()
panic("Crash")
fmt.Println("Program continues")
}

C. func main() {
panic("Crash")
defer func() {
if r := recover(); r != nil {
fmt.Println("Panic caught:", r)
}
}()
fmt.Println("Program continues")
}

D. func main() {
defer fmt.Println("Program continues")
panic("Crash")
}

Solution

1. Step 1: Check defer and recover placement

   func main() { defer func() { if r := recover(); r != nil { fmt.Println("Panic caught:", r) } }() panic("Crash") fmt.Println("Program continues") } correctly defers a function that calls recover() to catch panic and print a message.

2. Step 2: Verify program flow

   After panic, deferred recover runs, preventing crash and allowing program to continue, executing code after panic.

3. Final Answer:

   Uses defer func() with recover() before panic("Crash") -> Option B

4. Quick Check:

   defer + recover to catch panic = A [OK]

Hint: Defer recover before panic to handle it safely [OK]

Common Mistakes:

• Calling recover() outside defer
• Placing defer after panic
• Not handling panic at all