Value receivers in Go - Time & Space Complexity

Time Complexity: Value receivers

O(n)

Understanding Time Complexity

When using value receivers in Go methods, it's important to understand how the method call cost changes as the data size grows.

We want to see how the time to call a method with a value receiver grows when the struct size increases.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

    type Data struct {
      values [1000]int
    }

    func (d Data) Process() {
      // Imagine some processing here
    }

    func main() {
      d := Data{}
      d.Process()
    }
    

This code defines a struct with a large array and a method with a value receiver. The method is called on an instance.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Copying the entire struct when calling the method with a value receiver.
• How many times: Once per method call, but the cost depends on the struct size.

How Execution Grows With Input

As the struct size grows, the time to copy it for the value receiver grows proportionally.

Input Size (struct size)	Approx. Operations (copy cost)
10 ints	10 copy operations
100 ints	100 copy operations
1000 ints	1000 copy operations

Pattern observation: The copying work grows linearly with the struct size.

Final Time Complexity

Time Complexity: O(n)

This means the time to call the method grows in direct proportion to the size of the struct being copied.

Common Mistake

[X] Wrong: "Calling a method with a value receiver always takes constant time regardless of struct size."

[OK] Correct: Because Go copies the entire struct when using a value receiver, larger structs take more time to copy, so the cost grows with size.

Interview Connect

Understanding how value receivers affect performance helps you write efficient Go code and explain your choices clearly in discussions.

Self-Check

"What if we changed the method to use a pointer receiver instead? How would the time complexity change?"