Pointer receivers in Go - Step-by-Step Execution

Concept Flow - Pointer receivers

Define struct

↓

Define method with pointer receiver

↓

Create struct instance

↓

Call method on instance

↓

Method receives pointer

↓

Modify struct fields

↓

Changes visible outside method

This flow shows how a method with a pointer receiver modifies the original struct instance by receiving its memory address.

Execution Sample

Go

package main
import "fmt"
type Counter struct { count int }
func (c *Counter) Increment() { c.count++ }
func main() {
 c := Counter{}
 c.Increment()
 fmt.Println(c.count)
}

This code defines a struct with a pointer receiver method that increments a field, showing the change persists after the method call.

Execution Table

Step	Action	Receiver (c)	Field c.count	Output
1	Create Counter instance c	Counter{count:0}	0
2	Call c.Increment()	&c (pointer to c)	0 before increment
3	Inside Increment(), c.count++	&c	1 after increment
4	Return from Increment()	&c	1
5	Print c.count	Counter{count:1}	1	1

💡 Method call finished, c.count is updated to 1 and printed

Variable Tracker

Variable	Start	After Increment call	Final
c.count	0	1	1

Key Moments - 2 Insights

Why does c.count change after calling Increment()?

Because Increment() uses a pointer receiver, it modifies the original struct's field directly, as shown in step 3 and 4 of the execution_table.

What if Increment() used a value receiver instead of a pointer?

Then Increment() would work on a copy of c, so changes to c.count inside the method would not affect the original, unlike the pointer receiver case in the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of c.count immediately after step 3?

A 0

B 1

C Undefined

D 2

💡 Hint

Check the 'Field c.count' column at step 3 in the execution_table.

At which step does the method receive a pointer to the struct?

A Step 1

B Step 4

C Step 2

D Step 5

💡 Hint

Look at the 'Receiver (c)' column to see when &c is passed.

If Increment() used a value receiver, what would be the output at step 5?

A 0

B 1

C Compilation error

D Undefined

💡 Hint

Recall that value receivers work on copies, so original c.count remains unchanged.

Concept Snapshot

Pointer receivers in Go methods:
- Use *Type to define pointer receiver
- Method receives address, can modify original struct
- Changes inside method affect caller's instance
- Use pointer receivers to avoid copying large structs
- Enables modifying struct fields directly

Full Transcript

This example shows a Go struct Counter with a method Increment that uses a pointer receiver. When main creates an instance c and calls c.Increment(), the method receives a pointer to c, allowing it to increase the count field directly. The execution table traces each step: creation of c with count 0, calling Increment which receives &c, incrementing count to 1, returning, and finally printing the updated count 1. Key points include that pointer receivers allow methods to modify the original struct, unlike value receivers which work on copies. The visual quiz tests understanding of when the pointer is received, the value changes, and the effect of using value receivers. This helps beginners see how pointer receivers enable methods to change struct data in Go.

Practice

1. What is the main benefit of using a pointer receiver in Go methods?

easy

A. It allows the method to modify the original struct data.

B. It makes the method run faster by using multiple CPU cores.

C. It automatically creates a copy of the struct for safety.

D. It prevents the method from accessing struct fields.

Solution

1. Step 1: Understand pointer receiver purpose

   Pointer receivers let methods access and change the original struct, not a copy.

2. Step 2: Compare with value receivers

   Value receivers get a copy, so changes inside the method don't affect the original struct.

3. Final Answer:

   It allows the method to modify the original struct data. -> Option A

4. Quick Check:

   Pointer receiver modifies original struct = A [OK]

Hint: Pointer receivers let methods change original data directly [OK]

Common Mistakes:

• Thinking pointer receivers run methods on copies
• Confusing pointer receivers with concurrency
• Believing pointer receivers prevent access to fields

2. Which of the following is the correct syntax to define a method with a pointer receiver for struct Person?

easy

A. func (p *Person) UpdateName(name string) {}

B. func (p Person) UpdateName(name string) {}

C. func UpdateName(p Person, name string) {}

D. func UpdateName(*Person p, name string) {}

Solution

1. Step 1: Identify pointer receiver syntax

   Pointer receiver syntax uses (p *Person) before method name.

2. Step 2: Check each option

   func (p *Person) UpdateName(name string) {} correctly uses func (p *Person) UpdateName(name string) {}. Others either use value receiver or wrong syntax.

3. Final Answer:

   func (p *Person) UpdateName(name string) {} -> Option A

4. Quick Check:

   Pointer receiver syntax = (p *Person) [OK]

Hint: Pointer receiver always uses * before struct name in method receiver [OK]

Common Mistakes:

• Using value receiver syntax instead of pointer
• Placing * incorrectly in function parameters
• Confusing method receiver with function parameters

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

package main
import "fmt"
type Counter struct { value int }
func (c *Counter) Increment() { c.value++ }
func main() {
 c := Counter{value: 5}
 c.Increment()
 fmt.Println(c.value)
}

medium

A. 5

B. Compilation error

C. 0

D. 6

Solution

1. Step 1: Understand method call with pointer receiver

   The method Increment has a pointer receiver, so it modifies the original Counter struct's value.

2. Step 2: Trace the code execution

   Initial value is 5, calling Increment() increases it by 1, so value becomes 6. Then it prints 6.

3. Final Answer:

   6 -> Option D

4. Quick Check:

   Pointer receiver increments original value = 6 [OK]

Hint: Pointer receiver methods change original struct values [OK]

Common Mistakes:

• Assuming value receiver copies and does not change original
• Expecting output 5 without increment
• Thinking code causes compile error

4. Identify the error in this Go code snippet:

package main
import "fmt"
type Item struct { count int }
func (i Item) Increase() { i.count++ }
func main() {
 item := Item{count: 10}
 item.Increase()
 fmt.Println(item.count)
}

medium

A. Struct Item is missing a field tag.

B. fmt.Println cannot print struct fields directly.

C. Method Increase should have a pointer receiver to modify count.

D. Increase method must return the new count.

Solution

1. Step 1: Analyze method receiver type

   The method Increase uses a value receiver, so it works on a copy of Item.

2. Step 2: Understand effect on original struct

   Since it modifies the copy, the original item.count remains unchanged at 10.

3. Final Answer:

   Method Increase should have a pointer receiver to modify count. -> Option C

4. Quick Check:

   Value receiver does not change original struct = B [OK]

Hint: Use pointer receiver to modify struct fields inside methods [OK]

Common Mistakes:

• Thinking value receiver modifies original struct
• Believing fmt.Println can't print fields
• Expecting method must return value to update

5. You want to create a method Reset for struct Timer that sets its seconds field to zero. Which approach correctly uses pointer receivers to ensure the original Timer is reset?

type Timer struct { seconds int }
// Choose the correct Reset method:

hard

A. func (t Timer) Reset() { t.seconds = 0 }

B. func (t *Timer) Reset() { t.seconds = 0 }

C. func Reset(t Timer) { t.seconds = 0 }

D. func Reset(t *Timer) int { t.seconds = 0; return t.seconds }

Solution

1. Step 1: Understand method receiver for modifying struct

   To modify the original Timer, the method must have a pointer receiver (t *Timer).

2. Step 2: Check each option's effect

   The pointer receiver func (t *Timer) Reset() { t.seconds = 0 } correctly modifies the original struct. The value receiver version works on a copy, so changes won't persist. The plain function signatures are not methods attached to the Timer type, and returning a value is unnecessary for a reset operation.

3. Final Answer:

   func (t *Timer) Reset() { t.seconds = 0 } -> Option B

4. Quick Check:

   Pointer receiver method resets original struct = C [OK]

Hint: Reset original struct fields with pointer receiver methods [OK]

Common Mistakes:

• Using value receiver and expecting original change
• Confusing functions with methods
• Returning value unnecessarily in reset method