Why Custom error types in Go? - Purpose & Use Cases

The Big Idea

What if your program could tell you exactly what went wrong, instead of just saying "error"?

The Scenario

Imagine you write a program that talks to a bank system. When something goes wrong, you just get a generic error message like "something went wrong". You have to guess what happened and where. This makes fixing problems slow and frustrating.

The Problem

Using only generic errors is like getting a "404" on a website without knowing which page is missing. You waste time checking everything manually. It's easy to miss important details or confuse one error for another. This leads to bugs that are hard to find and fix.

The Solution

Custom error types let you create specific error messages with extra details. It's like having a special label on each problem that tells you exactly what went wrong and why. This makes your program smarter and easier to debug.

Before vs After

✗ Before

return errors.New("something went wrong")

✓ After

type InsufficientFundsError struct { Amount float64 }

func (e *InsufficientFundsError) Error() string {
    return fmt.Sprintf("insufficient funds: need %.2f more", e.Amount)
}

What It Enables

Custom error types let your program handle problems precisely and clearly, making it easier to fix bugs and improve user experience.

Real Life Example

When a bank app detects a withdrawal that exceeds the balance, a custom error can tell the user exactly how much more money is needed instead of a vague failure message.

Key Takeaways

Generic errors hide important details and slow debugging.

Custom error types add clear, specific information to errors.

This helps programs respond better and developers fix issues faster.