Go Error Handling Done Right: Patterns for Production Code

Introduction I'll be honest—when I first saw Go's error handling, I hated it. result, err := doSomething() if err != nil { return err } "Are you kidding me? I have to check errors after EVERY function call?" Coming from languages with try-catch ...