<div dir="ltr">I'm still in favor of adding `EitherT` to `transformers` in addition to `ErrorT`. The only person who disagreed the last discussion was Ross, so it's a matter of convincing him.</div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, Aug 13, 2013 at 1:36 AM, David Luposchainsky <span dir="ltr"><<a href="mailto:dluposchainsky@googlemail.com" target="_blank">dluposchainsky@googlemail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Morning,<br>
<br>
Another discussion that didn't reach conclusion: "Proposal to solve the<br>
`EitherT` problem." Let's do some proposal cleanup :-)<br>
<div class="im"><br>
On 2013-06-16 23:52, Gabriel Gonzalez wrote:<br>
<br>
> Approach 2: Add `EitherT` to `transformers` alongside `ErrorT` and<br>
have them both implement `MonadError`.<br>
<br>
</div>That's the one I would recommend.<br>
<br>
- Doesn't break anything, and gets rid of the "exception-vs-error"<br>
discussion.<br>
<br>
- Not all uses of Either are to distinguish between success and failure,<br>
sometimes it's just a convenient way of short-circuiting.<br>
<br>
- Fits in well with all the other transformers of type "MonadT".<br>
<br>
- MonadError instance makes possible use as throw-catch-y transformer clear.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
David<br>
</font></span></blockquote></div><br></div>