Interface definition in Go

Introduction

An interface in Go lets you define a set of actions (methods) that a type can do. It helps different types work together if they share these actions.

When you want different types to share common behavior without being the same type.

When you want to write functions that can work with many types as long as they follow certain rules.

When you want to separate what something does from how it does it.

When you want to make your code easier to test by using fake versions of types.

When you want to design flexible programs that can grow or change easily.

Syntax

Go

type InterfaceName interface {
    MethodName1(param1 Type1, param2 Type2) ReturnType
    MethodName2() ReturnType
}

Interfaces list method signatures without any code inside.

Any type that has these methods automatically implements the interface.

Examples

This interface requires a Speak method that returns a string.

Go

type Speaker interface {
    Speak() string
}

This interface requires a Read method that takes a byte slice and returns a number and an error.

Go

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

This interface requires two methods: Log and Error, each with different parameters.

Go

type Logger interface {
    Log(message string)
    Error(err error)
}

Sample Program

This program defines a Greeter interface with one method Greet. The Person type has a Greet method, so it implements Greeter. The sayHello function accepts any Greeter and calls Greet. In main, we create a Person and pass it to sayHello, which prints a greeting.

Go

package main

import "fmt"

// Define an interface
 type Greeter interface {
    Greet() string
}

// Define a type that implements Greeter
 type Person struct {
    name string
}

func (p Person) Greet() string {
    return "Hello, " + p.name
}

func sayHello(g Greeter) {
    fmt.Println(g.Greet())
}

func main() {
    p := Person{name: "Alice"}
    sayHello(p)
}

Important Notes

In Go, you don't need to explicitly say a type implements an interface; it happens automatically if methods match.

Interfaces help write flexible and testable code by focusing on behavior, not concrete types.

Summary

Interfaces define a set of methods without implementation.

Any type with those methods implements the interface automatically.

Interfaces let you write flexible code that works with many types.

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