Why methods are used in Go - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use methods in Go?

Why do programmers use methods in Go instead of just functions?

A Methods are only used to hide code from other programmers.

B Methods run faster than functions because they use special Go hardware instructions.

C Methods automatically make programs run in parallel without extra code.

D Methods allow functions to be associated with specific data types, making code organized and easier to understand.

💡 Hint

Think about how methods help group actions with the data they work on.

Methods let you attach functions to types, so you can call them directly on values of that type. This keeps related code together and makes programs easier to read and maintain.

❓ Predict Output

intermediate

Output of method call on struct

What is the output of this Go program?

Go

package main
import "fmt"
type Person struct {
  name string
}
func (p Person) greet() string {
  return "Hello, " + p.name
}
func main() {
  p := Person{name: "Anna"}
  fmt.Println(p.greet())
}

A Compilation error

B Hello,

C Hello, Anna

D p.greet

💡 Hint

Look at how the method uses the receiver to access the name field.

The method greet() is called on the Person value p. It returns "Hello, " plus the name field, which is "Anna".

🔧 Debug

advanced

Why does this method not modify the struct?

Consider this Go code. Why does the method not change the original struct's field?

Go

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)
}

A Because the method has a value receiver, it works on a copy, so the original count is unchanged.

B Because the increment method is missing a return statement.

C Because Go does not allow modifying struct fields inside methods.

D Because the count field is private and cannot be changed.

💡 Hint

Think about how Go passes the receiver to the method.

Methods with value receivers get a copy of the struct. Changes inside the method affect only the copy, not the original.

📝 Syntax

advanced

Identify the correct method declaration

Which option shows the correct way to declare a method named describe for a struct type Book in Go?

A func (b Book) describe() string { return b.title }

B func describe(b Book) string { return b.title }

C func (Book) describe() string { return title }

D func (b *Book) describe { return b.title }

💡 Hint

Remember method syntax requires receiver in parentheses and a return type if returning a value.

Option A correctly declares a method with receiver b Book, method name describe, and return type string.

🚀 Application

expert

Choosing pointer vs value receiver for methods

Given a struct Account with a method Deposit that adds money to the balance, which method receiver choice is best and why?

A Use a value receiver because it is safer to avoid changing the original data.

B Use a pointer receiver so the method can modify the original Account's balance.

C Use a pointer receiver only if the struct has more than 10 fields.

D Use a value receiver and return the new Account with updated balance.

💡 Hint

Think about whether the method needs to change the original data or just read it.

To update the balance inside the method, the receiver must be a pointer so changes affect the original struct.

Practice

1. Why do we use methods in Go programming language?

easy

A. To avoid using variables in the program

B. To write code that runs faster than functions

C. To associate functions with specific data types for better organization

D. To create global variables automatically

Solution

1. Step 1: Understand the purpose of methods

   Methods are functions tied to a specific data type, helping organize code logically.

2. Step 2: Compare methods with other options

   Options A, B, and D describe unrelated or incorrect uses of methods.

3. Final Answer:

   To associate functions with specific data types for better organization -> Option C

4. Quick Check:

   Methods connect actions to types = C [OK]

Hint: Methods link functions to types for clear code structure [OK]

Common Mistakes:

• Thinking methods make code run faster
• Confusing methods with variables
• Believing methods create global variables

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

easy

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

B. func UpdateName(p Person*, newName string) {}

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

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

Solution

1. Step 1: Recall Go method syntax with pointer receiver

   The receiver is declared inside parentheses before the method name, with *Type for pointer.

2. Step 2: Check each option

   func (p *Person) UpdateName(newName string) {} matches correct syntax: func (p *Person) MethodName(params) {}. Others have syntax errors.

3. Final Answer:

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

4. Quick Check:

   Pointer receiver syntax = D [OK]

Hint: Pointer receiver syntax: func (p *Type) method() {} [OK]

Common Mistakes:

• Placing * outside parentheses
• Using * in parameter list incorrectly
• Missing parentheses around receiver

3. What will be the output of the following Go code?

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. 6

B. 5

C. 0

D. Compilation error

Solution

1. Step 1: Understand pointer receiver effect

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

2. Step 2: Trace the code execution

   Initial value is 5, Increment adds 1, so value becomes 6, which is printed.

3. Final Answer:

   6 -> Option A

4. Quick Check:

   Pointer receiver changes value = 6 [OK]

Hint: Pointer receiver methods modify original data, so value changes [OK]

Common Mistakes:

• Thinking value stays 5 because method looks like a copy
• Assuming no output due to missing import
• Confusing pointer and value receivers

4. Identify the error in this Go method definition and fix it:

type Rectangle struct {
    width, height int
}

func (r Rectangle) Scale(factor int) {
    r.width = r.width * factor
    r.height = r.height * factor
}

medium

A. Change method name to lowercase: func (r Rectangle) scale(factor int) {}

B. Add return type: func (r Rectangle) Scale(factor int) Rectangle {}

C. Remove receiver: func Scale(factor int) {}

D. Change receiver to pointer: func (r *Rectangle) Scale(factor int) {}

Solution

1. Step 1: Understand why Scale does not change Rectangle

   The receiver is a value copy, so changes inside Scale do not affect original Rectangle.

2. Step 2: Fix by using pointer receiver

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

3. Final Answer:

   Change receiver to pointer: func (r *Rectangle) Scale(factor int) {} -> Option D

4. Quick Check:

   Pointer receiver needed to modify data = A [OK]

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

Common Mistakes:

• Using value receiver when modification is needed
• Adding return type unnecessarily
• Changing method name case without reason

5. You want to create a method that updates a user's email in a struct and also logs the change. Which approach best uses methods to achieve this in Go?

hard

A. Define a value receiver method that returns a new struct with updated email and logs externally

B. Define a pointer receiver method to update email and call a separate logging function inside it

C. Use a global function to update email and logging without methods

D. Define a method without receiver that updates email and logs

Solution

1. Step 1: Understand method purpose and data modification

   Updating email requires changing the original struct, so pointer receiver is needed.

2. Step 2: Combine update and logging logically

   Method with pointer receiver can update email and call logging function internally for reuse and clarity.

3. Final Answer:

   Define a pointer receiver method to update email and call a separate logging function inside it -> Option B

4. Quick Check:

   Pointer receiver + internal logging = A [OK]

Hint: Use pointer receiver method to update and log together [OK]

Common Mistakes:

• Using value receiver and expecting original to change
• Separating update and logging outside methods unnecessarily
• Avoiding methods and using only global functions