Why interfaces are used in Go - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare an interface named Speaker.

Go

type Speaker interface { [1]() string }

Drag options to blanks, or click blank then click option'

ASpeak

BRun

CWalk

DJump

Attempts:

3 left

💡 Hint

Common Mistakes

Using unrelated method names like Run or Walk in the Speaker interface.

The interface method name should be Speak to define a Speaker interface.

2fill in blank

medium

Complete the code to implement the Speaker interface for type Person.

Go

func (p Person) [1]() string { return "Hello" }

Drag options to blanks, or click blank then click option'

ARun

BJump

CSpeak

DWalk

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different method name that does not match the interface.

The method Speak matches the interface method and implements Speaker.

3fill in blank

hard

Fix the error in the code to assign a Person to a Speaker variable.

Go

var s Speaker = [1]

Drag options to blanks, or click blank then click option'

Aint{}

BSpeaker{}

Cstring{}

DPerson{}

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to assign a type that does not implement Speaker.

Only a value of type Person that implements Speaker can be assigned to s.

4fill in blank

hard

Fill both blanks to create a function that accepts any Speaker and calls Speak.

Go

func greet(s [1]) string { return s.[2]() }

Drag options to blanks, or click blank then click option'

ASpeaker

BPerson

CSpeak

DHello

Attempts:

3 left

💡 Hint

Common Mistakes

Using concrete type Person instead of interface Speaker in the function parameter.

Calling a method name not defined in the interface.

The function parameter type should be Speaker and call the Speak method.

5fill in blank

hard

Fill all three blanks to create a map of Speakers and call Speak on each.

Go

speakers := map[string][1]{
	"alice": [2]{},
}
for name, sp := range speakers {
	println(name, sp.[3]())
}

Drag options to blanks, or click blank then click option'

ASpeaker

BPerson

CSpeak

DHello

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong map value type.

Using wrong struct type for the map value.

Calling a method not defined in the interface.

The map holds values of interface type Speaker. The value is a Person struct. The method called is Speak.

Practice

1. Why are interfaces used in Go programming?

easy

A. To define a set of methods that different types can implement

B. To store data in a fixed format

C. To create variables with fixed values

D. To perform arithmetic operations

Solution

1. Step 1: Understand what interfaces represent

   Interfaces in Go define behavior by specifying method signatures without implementation.

2. Step 2: Recognize the purpose of interfaces

   They allow different types to implement the same set of methods, enabling flexible and interchangeable code.

3. Final Answer:

   To define a set of methods that different types can implement -> Option A

4. Quick Check:

   Interfaces define behavior = D [OK]

Hint: Interfaces describe behavior, not data storage [OK]

Common Mistakes:

• Thinking interfaces store data
• Confusing interfaces with variables
• Assuming interfaces perform calculations

2. Which of the following is the correct way to declare an interface in Go?

easy

A. interface Reader { Read(p []byte) (n int, err error) }

B. type Reader interface { Read(p []byte) (n int, err error) }

C. func Reader interface { Read(p []byte) (n int, err error) }

D. var Reader interface = { Read(p []byte) (n int, err error) }

Solution

1. Step 1: Recall Go syntax for interface declaration

   Interfaces are declared using the 'type' keyword followed by the interface name and the 'interface' keyword with method signatures inside curly braces.

2. Step 2: Identify the correct syntax

   type Reader interface { Read(p []byte) (n int, err error) } correctly uses 'type Reader interface { ... }' syntax.

3. Final Answer:

   type Reader interface { Read(p []byte) (n int, err error) } -> Option B

4. Quick Check:

   Interface declaration starts with 'type' = A [OK]

Hint: Interfaces start with 'type Name interface' [OK]

Common Mistakes:

• Omitting 'type' keyword
• Using 'func' instead of 'type'
• Assigning interface to a variable incorrectly

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

package main
import "fmt"
type Speaker interface {
    Speak() string
}
type Dog struct {}
func (d Dog) Speak() string {
    return "Woof!"
}
func saySomething(s Speaker) {
    fmt.Println(s.Speak())
}
func main() {
    var d Dog
    saySomething(d)
}

medium

A. Woof!

B. Compilation error

C. Runtime panic

D. No output

Solution

1. Step 1: Understand interface implementation

   Dog type implements the Speaker interface by defining Speak() method returning "Woof!".

2. Step 2: Trace the function call

   saySomething is called with Dog instance, which calls Speak() and prints "Woof!".

3. Final Answer:

   Woof! -> Option A

4. Quick Check:

   Interface method called correctly = Woof! [OK]

Hint: Interface method calls print implemented method output [OK]

Common Mistakes:

• Expecting error due to interface
• Confusing method receiver types
• Thinking interface needs explicit declaration

4. Identify the error in this Go code using interfaces:

package main
import "fmt"
type Walker interface {
    Walk()
}
type Cat struct {}
func (c Cat) Walk() {
    fmt.Println("Cat walks")
}
func main() {
    var w Walker
    w.Walk()
}

medium

A. Syntax error in interface declaration

B. Cat does not implement Walker interface

C. Variable w is nil and calling Walk() causes runtime panic

D. Walk method should return a value

Solution

1. Step 1: Analyze variable initialization

   Variable w of type Walker is declared but not assigned any value, so it is nil.

2. Step 2: Understand method call on nil interface

   Calling w.Walk() on nil interface causes a runtime panic because no concrete type implements the method at runtime.

3. Final Answer:

   Variable w is nil and calling Walk() causes runtime panic -> Option C

4. Quick Check:

   Calling method on nil interface = panic [OK]

Hint: Uninitialized interface variables cause runtime panic on method call [OK]

Common Mistakes:

• Assuming interface variable auto-initializes
• Thinking method must return value
• Confusing compile-time and runtime errors

5. You want to write a function that accepts any type that can Speak() and Walk(). How should you define the interface to achieve this in Go?

hard

A. Define two separate interfaces and pass both as parameters

B. Define an interface with only Speak method and ignore Walk

C. Use a struct with Speak and Walk methods instead of interface

D. Define a single interface embedding two interfaces: Speaker and Walker

Solution

1. Step 1: Understand interface embedding

   Go allows interfaces to embed other interfaces, combining their methods into one.

2. Step 2: Define combined interface

   By embedding Speaker and Walker interfaces, the new interface requires both Speak() and Walk() methods.

3. Final Answer:

   Define a single interface embedding two interfaces: Speaker and Walker -> Option D

4. Quick Check:

   Interface embedding combines behaviors = B [OK]

Hint: Embed interfaces to combine behaviors in one [OK]

Common Mistakes:

• Passing multiple interfaces separately instead of one
• Using struct instead of interface for behavior
• Ignoring one required method in interface