errors

> Not only do you constantly have to wrap and unwrap potential error values to unify different error types This is a legitimate issue, although in Haskell you can use one error type like Go does if you want to. > And as if that wasn't bad enough, there are also actual throw-catch-style exceptions, which are not checked in anyway This is also the case in Go (panics and recover). > I stopped writing Haskell maybe a year ago, but at least back then getting GHC to print a stack trace when an exception wasn't caught was a major feat that involved recompiling every single one of your hundreds of dependencies with profiling flags. This is also the case in Go. Errors do not retain anything about their state. You need to use a package like https://github.com/go-errors/errors, which has the exact same issue you describe with dependencies.