Interface definition in Go - Mini Project: Build & Apply

Interface definition

📖 Scenario: You are building a simple program to represent different types of vehicles. Each vehicle can describe itself by returning its type as a string.

🎯 Goal: Create an interface called Vehicle with a method Type() that returns a string. Then create two structs Car and Bike that implement this interface.

📋 What You'll Learn

Create an interface named Vehicle with a method Type() string

Create a struct named Car

Create a struct named Bike

Implement the Type() method for both Car and Bike to return their type as a string

Create variables of type Car and Bike

Use the Vehicle interface to call the Type() method on both variables

Print the results

💡 Why This Matters

🌍 Real World

Interfaces let you write code that works with different types in a uniform way, like handling different vehicles in a transport app.

💼 Career

Understanding interfaces is key for Go developers to build modular, testable, and maintainable software.

1

Create structs for vehicles

Create two structs called Car and Bike with no fields.

Go

# Your code here
// Define struct Car
// Define struct Bike

Hint

Use the type keyword to define structs with empty braces {}.

2

Define the Vehicle interface

Create an interface called Vehicle with a method Type() string.

Go

package main

type Car struct{}
type Bike struct{}

// Define interface Vehicle with method Type() string
# Your code here

Hint

Use type Vehicle interface { Type() string } to define the interface.

3

Implement the Type() method for Car and Bike

Write the Type() method for Car that returns "Car" and for Bike that returns "Bike".

Go

package main

type Car struct{}
type Bike struct{}

type Vehicle interface {
	Type() string
}

// Implement Type() for Car
// Implement Type() for Bike
# Your code here

Hint

Define methods with receiver types Car and Bike that return the correct string.

4

Use the Vehicle interface and print results

Create variables myCar of type Car and myBike of type Bike. Then create variables v1 and v2 of type Vehicle assigned to myCar and myBike. Finally, print the results of calling Type() on v1 and v2.

Go

package main

type Car struct{}
type Bike struct{}

type Vehicle interface {
	Type() string
}

func (c Car) Type() string {
	return "Car"
}

func (b Bike) Type() string {
	return "Bike"
}

func main() {
	// Create variable myCar of type Car
	// Create variable myBike of type Bike
	// Create variable v1 of type Vehicle assigned to myCar
	// Create variable v2 of type Vehicle assigned to myBike
	// Print v1.Type() and v2.Type()
# Your code here
}

Hint

Use var v1 Vehicle = myCar to assign the struct to the interface variable. Use println() to print the results.

Practice

1. What does an interface in Go define?

easy

A. A concrete type with fields and methods

B. A variable that holds data

C. A set of method signatures without implementation

D. A function that returns multiple values

Solution

1. Step 1: Understand what an interface is

   An interface in Go specifies method signatures but does not provide their implementation.

2. Step 2: Differentiate from other types

   Concrete types have fields and method implementations, unlike interfaces.

3. Final Answer:

   A set of method signatures without implementation -> Option C

4. Quick Check:

   Interface = method signatures only [OK]

Hint: Interfaces list methods only, no code inside [OK]

Common Mistakes:

• Thinking interfaces hold data
• Confusing interfaces with structs
• Assuming interfaces implement methods

2. Which of the following is the correct syntax to define an interface named Shape with a method Area() returning a float64?

easy

A. func Shape interface { Area() float64 }

B. interface Shape { func Area() float64 }

C. type Shape struct { Area() float64 }

D. type Shape interface { Area() float64 }

Solution

1. Step 1: Recall Go interface syntax

   Interfaces are defined with the keyword type, name, then interface and method signatures inside braces.

2. Step 2: Check each option

   type Shape interface { Area() float64 } matches correct syntax. Options B, C, and D misuse keywords or structure.

3. Final Answer:

   type Shape interface { Area() float64 } -> Option D

4. Quick Check:

   Correct interface syntax = type Shape interface { Area() float64 } [OK]

Hint: Use 'type Name interface { methods }' for interfaces [OK]

Common Mistakes:

• Using 'interface' keyword alone without 'type'
• Defining methods inside struct instead of interface
• Placing 'func' keyword inside interface method

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

package main
import "fmt"
type Printer interface {
    Print()
}
type Document struct {
    content string
}
func (d Document) Print() {
    fmt.Println(d.content)
}
func main() {
    var p Printer
    d := Document{"Hello, Go!"}
    p = d
    p.Print()
}

medium

A. Runtime panic: nil pointer dereference

B. Hello, Go!

C. Compilation error: cannot assign Document to Printer

D. No output

Solution

1. Step 1: Check interface implementation

   Document has a method Print() matching Printer interface, so Document implements Printer.

2. Step 2: Assign and call method

   Variable p of type Printer is assigned d (Document), then p.Print() calls Document.Print(), printing content.

3. Final Answer:

   Hello, Go! -> Option B

4. Quick Check:

   Interface method calls concrete method [OK]

Hint: Assign concrete type with matching methods to interface [OK]

Common Mistakes:

• Thinking interface needs explicit implementation declaration
• Expecting compile error on assignment
• Assuming interface variable is nil

4. Identify the error in this Go code snippet:

type Reader interface {
    Read(p []byte) (n int, err error)
}
type File struct {}
func (f File) Read() (int, error) {
    return 0, nil
}

medium

A. Method Read has wrong signature, missing parameter

B. File does not implement Reader because it lacks Read method

C. Interface Reader cannot have methods with parameters

D. No error, code is correct

Solution

1. Step 1: Compare method signatures

   Reader interface expects Read with parameter []byte and two return values.

2. Step 2: Check File's Read method

   File's Read method has no parameters, so signature does not match interface.

3. Final Answer:

   Method Read has wrong signature, missing parameter -> Option A

4. Quick Check:

   Method signature must match interface [OK]

Hint: Method signatures must exactly match interface methods [OK]

Common Mistakes:

• Ignoring method parameters in implementation
• Assuming method name alone is enough
• Thinking interface methods can't have parameters

5. Given these interfaces and types:

type Reader interface {
    Read(p []byte) (n int, err error)
}
type Writer interface {
    Write(p []byte) (n int, err error)
}
type ReadWriter interface {
    Reader
    Writer
}
type MyFile struct {}
func (f MyFile) Read(p []byte) (int, error) {
    return len(p), nil
}
func (f MyFile) Write(p []byte) (int, error) {
    return len(p), nil
}

Which statement is true about MyFile and ReadWriter?

hard

A. MyFile implements ReadWriter because it has both Read and Write methods

B. MyFile only implements Reader, not ReadWriter

C. MyFile does not implement any interface

D. ReadWriter cannot embed other interfaces

Solution

1. Step 1: Understand interface embedding

   ReadWriter embeds Reader and Writer, so it requires both methods.

2. Step 2: Check MyFile methods

   MyFile has both Read and Write methods matching signatures.

3. Step 3: Confirm implementation

   Since MyFile has all required methods, it implements ReadWriter.

4. Final Answer:

   MyFile implements ReadWriter because it has both Read and Write methods -> Option A

5. Quick Check:

   Embedded interfaces require all methods [OK]

Hint: Embedded interfaces combine methods; implement all to satisfy [OK]

Common Mistakes:

• Thinking embedding interfaces is invalid
• Assuming partial method implementation suffices
• Confusing interface embedding with inheritance