News for hackers. Stuff that matters.
Re:Everyday hassles in Go by Peaker on Tuesday December 30, 2014 @02:52PM (#8816349)
Proper sum types aren't enough to replace exceptions.

Imagine every IO action having its own error type in a sum type. How do you compose them?

Composing the different error types wouldn't unify.

The best attempt I've seen in Haskell is the control-monad-exception[1] library, but I'm not sure how well that would interact with everything.

[1] https://hackage.haskell.org/package/control-monad-exception

Re:Everyday hassles in Go by danidiaz on Tuesday December 30, 2014 @03:49PM (#8816667)
> Imagine every IO action having its own error type in a sum type. How do you compose them?

Perhaps by converting each error type to a common sum type. Something like "Either (Either error1 error2) result". Typeclasses like "Bifunctor" are quite useful for massaging the errors around:

http://hackage.haskell.org/package/bifunctors-4.2/docs/Data-...

Asynchronous exceptions do pose a problem for this approach though, as they can pop up in any function at any time. And perhaps a fully sum-type-based approach would clutter function signatures too much anyway.

Re:Everyday hassles in Go by adrusi on Tuesday December 30, 2014 @03:40PM (#8816619)
Check out how rust handles error composition using its Result type