Haskell is an evolving language and the error story isn't entirely resolved yet. Personally, I like the MonadThrow stategy which gives the flexibility to the c

Haskell is an evolving language and the error story isn't entirely resolved yet. Personally, I like the MonadThrow stategy which gives the flexibility to the caller but the IO story gets in the way. So yes, it can be messy when using other people's code because this is very much an unstable part of the language right now. I still prefer that over the worst possible strategy (what Go picked) being effectively baked in.