This is completely wrong. Result is either success or failure, so an R<E1, R<E2, A>> can never contain both E1 and E2 at the same time.
Validation types work the way you describe and require a monoidal "error" side, but famously do not form monads (though they are applicative functors).
Re:Mental models around Ok-Wrapping
by pinopinopino on Friday April 10, 2020 @11:58AM
(#22834324)
A true that, long day and have been working with shapeless in scala, where type level and value level mixes up :)
While compelling, flattening doesn't make something a monad, does it? Not snark, if that's a consequence of one of the three laws, I'm just unaware of it. I know what monads are but I'm not practised with them.
But of left identity, right identity, and associativity, what is violated?
Re:Mental models around Ok-Wrapping
by pinopinopino on Friday April 10, 2020 @12:08PM
(#22834404)
So, I was a bit wrong with the monoid, I meant to add them on typelevel by using a sumtype. Sorry, sometimes bit confused after work.
No flattening doesn't make something a monad. Return and flattening are the interesting operations of a monad, that together with the laws makes the monad.
>But of left identity, right identity, and associativity, what is violated?
Well, there is not something violated perse, but you cannot write a flatten operation for something like this:
R<R<u32, E1>, E2>
However you could write it for this: R<R<u32, E1 + E2>, E1 + E2>
(That was what I should have written above btw) Because now the error types are the same.
You need to think up a reasonable implementation of +. This is of course easily solvable, you can just add them together. Keep a list of errors in your result instead of one error and you are done. Just keep the +, it is free :p