Function parameters in Go - Time & Space Complexity

Time Complexity: Function parameters

O(n)

Understanding Time Complexity

When we use function parameters, we want to know how the time to run the function changes as the input changes.

We ask: How does the size or number of parameters affect the work the function does?

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 the numbers given in a list and returns the total.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through each number in the list.
• How many times: Once for every number in the input 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; double the items, double the work.

Final Time Complexity

Time Complexity: O(n)

This means the time to finish grows in a straight line with the number of input items.

Common Mistake

[X] Wrong: "Function parameters do not affect time because they are just inputs."

[OK] Correct: The size or amount of data passed as parameters can change how many steps the function takes, so it does affect time.

Interview Connect

Understanding how input size affects function time helps you explain your code clearly and shows you think about efficiency, a skill valued in real projects.

Self-Check

"What if the function took two lists instead of one? How would the time complexity change?"

Practice

1. What is the purpose of function parameters in Go?

easy

A. To print output from a function

B. To create new functions automatically

C. To stop a function from running

D. To send data into functions so they can use it

Solution

1. Step 1: Understand what parameters do

   Parameters let you give information to a function when you call it.

2. Step 2: Identify the correct purpose

   Sending data into functions makes them flexible and reusable with different inputs.

3. Final Answer:

   To send data into functions so they can use it -> Option D

4. Quick Check:

   Function parameters = send data into functions [OK]

Hint: Parameters pass data into functions for reuse [OK]

Common Mistakes:

• Thinking parameters create functions
• Confusing parameters with output
• Believing parameters stop function execution

2. Which of the following is the correct way to declare a function with two integer parameters in Go?

easy

A. func add(a, b int) int {}

B. func add(a int, b) int {}

C. func add(int a, int b) int {}

D. func add(a int b int) int {}

Solution

1. Step 1: Review Go function parameter syntax

   In Go, you can group parameters of the same type like a, b int.

2. Step 2: Identify correct syntax

   func add(a, b int) int {} groups same type parameters correctly. func add(a int, b) int {} misses type for b. func add(int a, int b) int {} places types before names. func add(a int b int) int {} lacks commas.

3. Final Answer:

   func add(a, b int) int {} -> Option A

4. Quick Check:

   Group same type params: a, b int [OK]

Hint: Group same type params with commas before type [OK]

Common Mistakes:

• Writing types before variable names (like C)
• Missing commas between parameters (like D)
• Forgetting type for second parameter (like B)

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

package main
import "fmt"
func greet(name string) {
    fmt.Println("Hello, " + name)
}
func main() {
    greet("Alice")
}

medium

A. Hello,

B. Hello, Alice

C. Hello, name

D. Compilation error

Solution

1. Step 1: Understand function call with parameter

   The function greet takes a string parameter name and prints "Hello, " plus that name.

2. Step 2: Check the argument passed

   In main, greet("Alice") is called, so name is "Alice".

3. Final Answer:

   Hello, Alice -> Option B

4. Quick Check:

   Function prints "Hello, " + argument [OK]

Hint: Function prints greeting plus passed name [OK]

Common Mistakes:

• Confusing parameter name with string literal
• Expecting no output
• Thinking it causes error without return

4. Identify the error in this Go function declaration:

func multiply(a int, b int) int {
    return a * b
}

func main() {
    result := multiply(3)
    fmt.Println(result)
}

medium

A. Function multiply called with wrong number of arguments

B. Missing import for fmt package

C. Return type missing in multiply function

D. Variable result not declared

Solution

1. Step 1: Check function call arguments

   The function multiply requires two int parameters, but it is called with only one argument 3.

2. Step 2: Identify the error

   This causes a compile-time error due to wrong number of arguments.

3. Final Answer:

   Function multiply called with wrong number of arguments -> Option A

4. Quick Check:

   Function call args must match parameters [OK]

Hint: Count arguments to match parameters exactly [OK]

Common Mistakes:

• Ignoring missing import for fmt (not shown here)
• Thinking return type is missing
• Assuming variable declaration error

5. Given this Go function:

func sumAndProduct(a, b int) (int, int) {
    return a + b, a * b
}

func main() {
    s, p := sumAndProduct(4, 5)
    fmt.Println(s, p)
}

What will be the output when the program runs?

hard

A. 20 9

B. 9

C. 9 20

D. Compilation error due to missing return

Solution

1. Step 1: Understand multiple return values

   The function sumAndProduct returns two integers: sum and product of a and b.

2. Step 2: Check values for inputs 4 and 5

   Sum is 4 + 5 = 9, product is 4 * 5 = 20. These are assigned to s and p.

3. Step 3: Print output

   fmt.Println(s, p) prints "9 20".

4. Final Answer:

   9 20 -> Option C

5. Quick Check:

   Multiple returns print sum then product [OK]

Hint: Multiple returns unpacked in order [OK]

Common Mistakes:

• Swapping sum and product values
• Expecting single return value
• Thinking missing return error