3 ms·
Curious why you're using fmt.Fprintf and not fmt.Errorf? Or is that a typo? And I think you're going to have problems with this pattern if you join a team usin
by marcus_holmes 3y ago
Curious why you're using fmt.Fprintf and not fmt.Errorf? Or is that a typo?
And I think you're going to have problems with this pattern if you join a team using Go in an organisation. The `if err != nil` pattern is the norm, and everyone's used to it (and the regular cadence of Go code; "do the thing, check the error, do the thing, check the error" is very readable).
- dpifke 3y agoThat was a typo, thanks for pointing it out. :)