Error typeclass

[ktonga]

In the same vein as Haskell's Exception

In addition to be just a marker TC it could have functions such as defaultError which could be useful to define a meaningful MonadPlus for IO

[fommil]

@emilypi ^^^

[jdegoes]

@ktonga Why not mzero(Monoid zero) for MonadPlus?

[ktonga]

That makes it harder to distinguish the empty IO (from other failed) in plus to hold the identity laws. It's not impossible, the implementation will differ from the one in Plus and we have to add Monoid and Equal constrains to E. If the default error is a singleton it is simpler and clearer.

[ktonga]

Another useful method could be isRetryable. I'm not saying we should mark E with it everywhere, just add the constraint when it makes sense and we can provide more functionality. For instance there could be two flavors of maybeRetry one with the constraint and another accepting an E => Boolean

[fommil]

@jdegoes check my comments about that. We can do it, but it will mean an object allocation, and requiring Equal[E] (as well as Monoid[E]), and we have to be careful about breaking coherence in the implicit priorities for the case where there is no Equal or Monoid.

https://github.com/scalaz/ioeffect/blob/master/ioeffect/src/main/scala/scalaz/ioeffect/IOInstances.scala#L48-L55

[fommil]

(I'll code it up so we can see exactyl what I mean...)

[fommil]

scalaz/ioeffect#61

[ktonga]

Monoidal E it is