Value receivers in Go - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a value receiver in Go methods?

A value receiver is when a method has a receiver argument that is a copy of the value, not a pointer. Changes inside the method do not affect the original value.

beginner

How does a value receiver differ from a pointer receiver?

A value receiver works on a copy of the value, so it cannot modify the original. A pointer receiver works on the original value via its memory address, allowing modifications.

intermediate

Can value receivers be used with both pointer and non-pointer values when calling methods?

Yes. When a method has a value receiver, you can call it on both pointer and non-pointer values. Go automatically handles the conversion.

intermediate

Why might you choose a value receiver over a pointer receiver?

Use value receivers when the method does not need to modify the original value and the value is small or cheap to copy, like basic types or small structs.

beginner

What happens if you modify a field inside a method with a value receiver?

Modifications affect only the copy inside the method. The original value outside the method remains unchanged.

What does a value receiver method receive in Go?

A A reference to the value

B A pointer to the value

C A copy of the value

D A global variable

A value receiver method receives a copy of the value, not a pointer or reference.

If you change a field inside a value receiver method, what happens to the original value?

A It changes

B It stays the same

C It causes an error

D It becomes nil

Changes inside a value receiver method affect only the copy, so the original value stays the same.

Can you call a value receiver method on a pointer to a struct?

A Only if the method is exported

B No, it causes a compile error

C Only if you use * operator

D Yes, Go converts automatically

Go automatically converts pointer to value when calling a value receiver method.

When is it better to use a value receiver?

A When the method does not modify the receiver and the value is small

B When you want to modify the original value

C When the value is very large

D When you want to share data between goroutines

Value receivers are good for small values and when no modification is needed.

Which of these is true about value receivers?

A They receive a copy and cannot modify the original

B They receive a pointer and can modify the original

C They always cause slower performance

D They can only be used with basic types

Value receivers get a copy and cannot change the original value.

Explain what a value receiver is and how it behaves when modifying fields inside its method.

Think about how changes inside the method affect the original variable.

Describe when you would choose a value receiver instead of a pointer receiver in Go methods.

Consider the size of the value and whether you want to change it.

Practice

1. What does a value receiver method in Go do when called on a struct?

easy

A. It requires a pointer to the struct to work.

B. It modifies the original struct directly.

C. It works on a copy of the struct, leaving the original unchanged.

D. It only works with built-in types, not structs.

Solution

1. Step 1: Understand value receiver behavior

   Value receivers get a copy of the struct, so changes inside the method do not affect the original.

2. Step 2: Compare with pointer receivers

   Pointer receivers work on the original struct, but value receivers do not.

3. Final Answer:

   It works on a copy of the struct, leaving the original unchanged. -> Option C

4. Quick Check:

   Value receiver = copy, no original change [OK]

Hint: Value receivers copy data; original stays safe [OK]

Common Mistakes:

• Thinking value receivers modify the original struct
• Confusing value and pointer receivers
• Assuming value receivers require pointers

2. Which of the following is the correct syntax to define a method with a value receiver in Go?

easy

A. func greet(p Person) {}

B. func (p Person) greet() {}

C. func (p *Person) greet() {}

D. func greet(*Person) {}

Solution

1. Step 1: Identify method receiver syntax

   Methods with receivers use the syntax: func (receiver Type) methodName() {}.

2. Step 2: Distinguish value vs pointer receiver

   Value receiver uses the type directly (e.g., Person), pointer receiver uses *Person.

3. Final Answer:

   func (p Person) greet() {} -> Option B

4. Quick Check:

   Value receiver syntax = func (p Type) method() [OK]

Hint: Value receiver uses type, pointer uses *type [OK]

Common Mistakes:

• Using pointer syntax for value receiver
• Defining method without receiver
• Confusing function parameter with method receiver

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

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

medium

A. 5

B. 6

C. 0

D. Compilation error

Solution

1. Step 1: Analyze increment method with value receiver

   The increment method uses a value receiver, so it works on a copy of Counter, not the original.

2. Step 2: Check effect on original Counter

   Incrementing c.count inside the method changes only the copy; original c.count remains 5.

3. Final Answer:

   5 -> Option A

4. Quick Check:

   Value receiver method does not change original value [OK]

Hint: Value receiver methods don't change original struct [OK]

Common Mistakes:

• Assuming increment changes original count
• Confusing value and pointer receivers
• Expecting output 6 instead of 5

4. Identify the problem in this Go code snippet and fix it:

type Point struct { x, y int }
func (p Point) move(dx, dy int) {
    p.x += dx
    p.y += dy
}
func main() {
    pt := Point{1, 2}
    pt.move(3, 4)
    fmt.Println(pt)
}

medium

A. Use global variables instead of struct fields

B. Return new Point from move method

C. No fix needed; code works as intended

D. Change method receiver to pointer: func (p *Point) move(dx, dy int)

Solution

1. Step 1: Understand why move method doesn't update original

   Method uses value receiver, so changes affect only a copy, not original Point.

2. Step 2: Fix by using pointer receiver

   Changing receiver to *Point allows method to modify original struct fields.

3. Final Answer:

   Change method receiver to pointer: func (p *Point) move(dx, dy int) -> Option D

4. Quick Check:

   Pointer receiver needed to modify original struct [OK]

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

Common Mistakes:

• Not using pointer receiver for modifying methods
• Trying to fix by returning new struct without assignment
• Ignoring that value receiver copies struct

5. You have a struct Book with a method Display() using a value receiver. You want to add a method UpdateTitle(newTitle string) that changes the title. Which is the best approach?

hard

A. Define UpdateTitle with a pointer receiver to modify the original Book.

B. Define UpdateTitle with a value receiver and assign the new title inside it.

C. Keep both methods with value receivers for consistency.

D. Make Display use a pointer receiver instead of value receiver.

Solution

1. Step 1: Understand method receiver choice for updating data

   To change the original struct, methods must use pointer receivers.

2. Step 2: Decide best practice for mixed methods

   It's fine to have Display use value receiver (read-only), and UpdateTitle use pointer receiver (modifies data).

3. Final Answer:

   Define UpdateTitle with a pointer receiver to modify the original Book. -> Option A

4. Quick Check:

   Modify method uses pointer receiver; read-only can use value [OK]

Hint: Use pointer receiver for methods that change data [OK]

Common Mistakes:

• Using value receiver for methods that modify struct
• Changing all methods to pointer receivers unnecessarily
• Confusing method consistency with receiver type