Function execution flow in Go - Time & Space Complexity

Time Complexity: Function execution flow

O(n)

Understanding Time Complexity

When we look at how a function runs, we want to know how long it takes as the input grows.

We ask: How does the work inside the function increase when input changes?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

func sum(numbers []int) int {
    total := 0
    for _, num := range numbers {
        total += num
    }
    return total
}

This function adds up all numbers in a list and returns the total.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Adding each number to total inside a loop.
• How many times: Once for every number in the list.

How Execution Grows With Input

As the list gets bigger, the function does more additions, one for each number.

Input Size (n)	Approx. Operations
10	10 additions
100	100 additions
1000	1000 additions

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 function runs in the same time no matter how many numbers there are."

[OK] Correct: Because the function must add each number, more numbers mean more work.

Interview Connect

Understanding how function steps grow with input helps you explain your code clearly and think about efficiency.

Self-Check

"What if we changed the function to sum only the first half of the list? How would the time complexity change?"

Practice

1. What happens when a function in Go is called?

easy

A. The code inside the function runs from top to bottom.

B. The program stops and waits for user input.

C. The function immediately returns without running any code.

D. The function runs only if it has no parameters.

Solution

1. Step 1: Understand function call behavior

   When a function is called, Go executes the code inside it in order, from the first line to the last.

2. Step 2: Eliminate incorrect options

   Options A, B, and C describe behaviors that are not how Go functions work when called.

3. Final Answer:

   The code inside the function runs from top to bottom. -> Option A

4. Quick Check:

   Function execution flow = top to bottom [OK]

Hint: Functions run code line by line when called [OK]

Common Mistakes:

• Thinking functions run only if no parameters
• Believing functions wait for user input automatically
• Assuming functions return immediately without running code

2. Which of the following is the correct way to define a function named greet that returns a string in Go?

easy

A. func greet() { return "Hello" }

B. function greet() { return "Hello" }

C. func greet() string { return "Hello" }

D. func greet() string { print("Hello") }

Solution

1. Step 1: Check Go function syntax

   In Go, functions start with func, followed by the name, parameters, and return type. func greet() string { return "Hello" } matches this.

2. Step 2: Verify return statement and type

   func greet() string { return "Hello" } returns a string and has the correct syntax. The version using 'function greet() { return "Hello" }' uses wrong keyword. The version 'func greet() { return "Hello" }' misses return type. The version using print instead of return is incorrect.

3. Final Answer:

   func greet() string { return "Hello" } -> Option C

4. Quick Check:

   Correct Go function syntax = func greet() string { return "Hello" } [OK]

Hint: Go functions start with func and specify return type [OK]

Common Mistakes:

• Using 'function' keyword instead of 'func'
• Omitting return type when function returns a value
• Using print instead of return for output

3. What is the output of this Go program?

package main
import "fmt"
func add(a int, b int) int {
    return a + b
}
func main() {
    result := add(3, 4)
    fmt.Println(result)
}

medium

A. 34

B. Compilation error

C. 0

D. 7

Solution

1. Step 1: Understand function call and return

   The function add takes two integers and returns their sum. Calling add(3, 4) returns 7.

2. Step 2: Check output statement

   fmt.Println(result) prints the returned value, which is 7.

3. Final Answer:

   7 -> Option D

4. Quick Check:

   3 + 4 = 7 [OK]

Hint: Add numbers inside function, print returned result [OK]

Common Mistakes:

• Concatenating numbers as strings (34)
• Expecting zero without return
• Thinking code has syntax errors

4. Identify the error in this Go function and select the fix:

func multiply(a int, b int) int {
    product := a * b
}

func main() {
    fmt.Println(multiply(2, 3))
}

medium

A. Change function to void (no return type)

B. Add a return statement: return product

C. Remove parameters a and b

D. Replace * with + operator

Solution

1. Step 1: Check function return type and body

   The function declares it returns an int but does not have a return statement, causing a compile error.

2. Step 2: Fix by adding return statement

   Adding return product returns the calculated value, matching the function signature.

3. Final Answer:

   Add a return statement: return product -> Option B

4. Quick Check:

   Function must return value if declared [OK]

Hint: Functions with return type must return a value [OK]

Common Mistakes:

• Forgetting return statement in non-void functions
• Changing function signature unnecessarily
• Changing operators without reason

5. Given this Go code, what will be printed?

package main
import "fmt"
func process(x int) int {
    if x > 0 {
        return x * 2
    }
    return 0
}
func main() {
    values := []int{3, -1, 0, 5}
    sum := 0
    for _, v := range values {
        sum += process(v)
    }
    fmt.Println(sum)
}

hard

A. 16

B. 8

C. 0

D. Compilation error

Solution

1. Step 1: Analyze function process behavior

   For each value, if positive, returns double the value; else returns 0.

2. Step 2: Calculate sum over values slice

   Values: 3 -> 6, -1 -> 0, 0 -> 0, 5 -> 10; sum = 6 + 0 + 0 + 10 = 16.

3. Final Answer:

   16 -> Option A

4. Quick Check:

   Sum of doubled positives = 16 [OK]

Hint: Sum doubles positives, zeros for others [OK]

Common Mistakes:

• Adding negative or zero values incorrectly
• Forgetting return 0 for non-positive
• Misreading loop or function logic