> Checking and handling all possible error conditions is a GOOD thing. I agree. But Go seems to have taken the most verbose way to achieve that. Pattern matchi

> Checking and handling all possible error conditions is a GOOD thing. I agree. But Go seems to have taken the most verbose way to achieve that. Pattern matching should have been the way to go if they did not want to use exceptions. Then again, Go does not have functional constructs, and you wouldn't be able to get far with it. Though it still prevents you from ignoring errors, unlike what exists in the language.