Pointer receivers in Go - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a pointer receiver in Go?

A pointer receiver is a method receiver that uses a pointer to the type, allowing the method to modify the original value the pointer points to.

beginner

Why use pointer receivers instead of value receivers?

Pointer receivers allow methods to modify the original struct, avoid copying large structs, and maintain consistency when some methods need to modify the receiver.

beginner

How do you declare a method with a pointer receiver in Go?

Use a receiver with a pointer type, for example:

func (p *Person) UpdateName(newName string) { p.Name = newName }

intermediate

What happens if you call a pointer receiver method on a value?

Go automatically takes the address of the value to call the pointer receiver method, so it works seamlessly without explicit pointers.

intermediate

Can pointer receivers be used with interfaces?

Yes, but only if the interface variable holds a pointer to the type. Methods with pointer receivers require the value to be a pointer to satisfy the interface.

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

A It prevents the method from modifying the struct.

B It allows the method to modify the original struct.

C It makes the method run faster by default.

D It automatically copies the struct before method call.

Pointer receivers let methods change the original struct by using its memory address.

How do you declare a pointer receiver method for a struct named Car?

A func (c *Car) Drive() {}

B func Drive(c *Car) {}

C func Drive(c Car) {}

D func (c Car) Drive() {}

Pointer receiver methods use a pointer in the receiver: (c *Car).

If you have a value of type Person, can you call a method with a pointer receiver on it?

A Only if the method does not modify the struct.

B No, you must use a pointer explicitly.

C Yes, Go automatically takes the address.

D Only if the struct is small.

Go automatically converts the value to a pointer when calling pointer receiver methods.

Which of these is true about interfaces and pointer receivers?

A Only pointer types can satisfy interfaces with pointer receiver methods.

B A value type can satisfy an interface with pointer receiver methods.

C Interfaces cannot have pointer receiver methods.

D Pointer receivers are ignored when implementing interfaces.

Interfaces require the method set to match; pointer receiver methods need pointer types to satisfy interfaces.

Why might you avoid using value receivers for large structs?

A Because value receivers can modify the original struct.

B Because value receivers cannot be used with methods.

C Because value receivers are slower to write.

D Because value receivers copy the entire struct, which is inefficient.

Value receivers copy the whole struct, which can be slow and use more memory for large structs.

Explain what a pointer receiver is and why it is useful in Go methods.

Think about how methods can change the data inside a struct.

Describe how Go handles calling pointer receiver methods on values and how this affects your code.

Consider what happens behind the scenes when you call a method.

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