Type inference in Go - Time & Space Complexity

Time Complexity: Type inference

O(n)

Understanding Time Complexity

Type inference helps the computer guess variable types automatically. We want to see how this guessing affects the program's speed.

Does type inference change how long the program takes to run?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

package main

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

func main() {
    nums := []int{1, 2, 3, 4, 5}
    _ = sum(nums)
}

This code sums all numbers in a list using type inference for variables.

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 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	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 list size.

Common Mistake

[X] Wrong: "Type inference makes the program slower because it guesses types at runtime."

[OK] Correct: Type inference happens when the program is compiled, so it does not slow down the running program.

Interview Connect

Understanding how type inference works helps you explain code clarity and performance. It shows you know how the language handles types behind the scenes.

Self-Check

"What if we changed the loop to a recursive function? How would the time complexity change?"

Practice

1. What does type inference mean in Go when you write x := 10 inside a function?

easy

A. You must tell Go the type of x explicitly.

B. Go automatically figures out that x is an int.

C. Go treats x as a string by default.

D. The variable x has no type.

Solution

1. Step 1: Understand the := operator in Go

   The := operator declares a variable and assigns a value, letting Go guess the type.

2. Step 2: Check the assigned value type

   Since 10 is an integer, Go infers the type of x as int automatically.

3. Final Answer:

   Go automatically figures out that x is an int. -> Option B

4. Quick Check:

   Type inference means Go guesses type from value [OK]

Hint: := means declare and infer type from value [OK]

Common Mistakes:

• Thinking you must always write the type explicitly
• Assuming variables have no type
• Believing Go defaults to string type

2. Which of the following is the correct way to declare and assign a variable with type inference inside a function in Go?

easy

A. x := 5

B. x = 5

C. var x int = 5

D. int x = 5

Solution

1. Step 1: Recall Go syntax for type inference

   Inside functions, := declares and assigns a variable with inferred type.

2. Step 2: Check each option

   var x int = 5 declares with explicit type, not inference. x = 5 misses declaration. int x = 5 is invalid Go syntax.

3. Final Answer:

   x := 5 -> Option A

4. Quick Check:

   Use := to declare and infer type [OK]

Hint: Use := inside functions for type inference [OK]

Common Mistakes:

• Using C or D which are invalid Go syntax
• Forgetting to declare variable before assignment
• Confusing var declaration with :=

3. What is the output of this Go program?

package main
import "fmt"
func main() {
    x := 3.14
    fmt.Printf("%T", x)
}

medium

A. float64

B. float32

C. int

D. string

Solution

1. Step 1: Identify the type inferred for 3.14

   In Go, untyped floating-point constants default to float64 when assigned with :=.

2. Step 2: Understand fmt.Printf with %T

   The %T verb prints the type of the variable, so it will print "float64".

3. Final Answer:

   float64 -> Option A

4. Quick Check:

   Float literals default to float64 [OK]

Hint: Float literals default to float64 type [OK]

Common Mistakes:

• Assuming float32 is default
• Thinking 3.14 is int
• Confusing %T output with value

4. What is wrong with this Go code snippet?

func main() {
    var x := 10
    fmt.Println(x)
}

medium

A. The value 10 is not a valid integer.

B. x is not declared before use.

C. You cannot use := with var keyword.

D. fmt.Println is not imported.

Solution

1. Step 1: Understand variable declaration syntax

   In Go, := is shorthand for declaration and assignment without var keyword.

2. Step 2: Identify the syntax error

   Using var and := together is invalid syntax; you must use either var x = 10 or x := 10.

3. Final Answer:

   You cannot use := with var keyword. -> Option C

4. Quick Check:

   var and := cannot be combined [OK]

Hint: Don't combine var and := in one statement [OK]

Common Mistakes:

• Mixing var and := together
• Ignoring import errors (not shown here)
• Thinking := works outside functions

5. Given this Go code, what is the type of result after execution?

func main() {
    a := 5
    b := 2.0
    result := a * int(b)
    fmt.Printf("%T", result)
}

hard

A. float64

B. string

C. float32

D. int

Solution

1. Step 1: Analyze variable types and conversion

   a is int, b is float64 (default for 2.0). The expression converts b to int before multiplication.

2. Step 2: Determine result type

   Multiplying int (a) by int (converted b) results in int type for result.

3. Final Answer:

   int -> Option D

4. Quick Check:

   int * int = int type [OK]

Hint: Type conversion affects result type [OK]

Common Mistakes:

• Assuming result is float64 without conversion
• Forgetting to convert float to int
• Confusing multiplication type rules