Reviewing golang code where forced error checking means 3 out of every 4 lines is repetitive error handling for errors that will likely never occur (but are not impossible).
Remind me why forced error checking is a good thing?
Conversation
Replying to
Trying not to avoid ranting about Go's error prone error handling approach… really trying! I get that error handling is a really challenging language design problem, but it's pretty hard for me to be sympathetic with Go's designers on their choices here. 🙄
