Go has no exceptions. Errors are values returned as the last result. Explicit checking is mandatory and idiomatic.

Basic Pattern 

  result, err := doSomething()
if err != nil {
    return fmt.Errorf("doSomething failed: %w", err)
}

Creating Errors 

  return fmt.Errorf("invalid input: %d", n)

var ErrNotFound = errors.New("not found")

errors.Is and errors.As 

  if errors.Is(err, ErrNotFound) { /* handle */ }

var pathErr *os.PathError
if errors.As(err, &pathErr) { fmt.Println(pathErr.Path) }

Custom Errors 

  type ValidationError struct {
    Field string
    Msg   string
}
func (e *ValidationError) Error() string {
    return fmt.Sprintf("%s: %s", e.Field, e.Msg)
}

Panic/Recover 

  // Only for truly unrecoverable situations
defer func() {
    if r := recover(); r != nil {
        log.Printf("recovered: %v", r)
    }
}()

Common Pitfalls

  • Ignoring returned errors in Go or fighting the borrow checker in Rust.
  • Premature optimization before profiling.
  • Skipping tests for concurrent and error paths.
  • Not reading standard library documentation.

Best Practices

  • Follow language idioms (Go: explicit errors; Rust: ownership).
  • Write table-driven tests.
  • Use go fmt / cargo fmt consistently.
  • Keep functions small and focused.

Memory and Performance Notes

Error interface is one method — zero allocation for sentinel errors.

Exercise

Wrap errors through 3 function layers using %w. Test with errors.Is.

Hint: Don’t panic for expected errors. Return error values instead.

Summary

Practice these concepts in small programs before building production services.

Debugging Checklist

  1. Read the full error message.
  2. Reduce to minimal reproduction.
  3. Check types and return values.
  4. Add logging at decision points.
  5. Write a test that catches the bug.

Real-World Application

Production services combine these fundamentals with logging, metrics, and graceful degradation.

Further Reading

Official language documentation, effective guides, and mature open-source projects.

Additional Examples

Consider how this topic applies in a larger project:

  // Break the problem into smaller functions
// Test each function independently
// Integrate incrementally

Working through variations of the examples above builds deeper understanding than reading alone.

Interview and Review Questions

  1. Explain the core concept of this topic in your own words.
  2. What happens when this code runs with edge-case input (empty, null, zero, max value)?
  3. How would you debug a bug related to this topic in production?
  4. What are the performance implications of the approach shown here?
  5. How does this feature compare to the equivalent in another language you know?

Review adjacent pages in the learning path before and after this one. Concepts build on each other — skipping ahead often leads to confusion when later pages assume mastery of earlier material.

Return to the section index if you need to fill gaps in prerequisite knowledge.

Tooling Tips

  • Enable all compiler or analyzer warnings during development.
  • Use version control with small, focused commits for each exercise.
  • Pair reading with typing — reproduce every code example by hand.
  • Run tests or compile after every change to catch errors early.
  • Keep a personal notes file linking concepts to your own project experiences.

Additional Examples

Consider how this topic applies in a larger project:

  // Break the problem into smaller functions
// Test each function independently
// Integrate incrementally

Working through variations of the examples above builds deeper understanding than reading alone.