4 ms·
Looking at the first example, "The "if err != nil" problem": note how errors got noticeable worse... If something breaks, you no longer know if it's fetch vs va
by theamk 11mo ago
Looking at the first example, "The "if err != nil" problem": note how errors got noticeable worse... If something breaks, you no longer know if it's fetch vs validation vs payment.
I am not an "establishment" but this terrifies me. Error message quality already took a nosedive when people switch from languages with backtraces into Go. Slowly, after pain of thousands debugging sessions, people are realizing that "return nil, err" is bad, and fmt.Errorf should be used everywhere. And how we have new languages undoing this all again?