Elegant Error Handling with the JavaScript “Either” Monad

Re:Elegant Error Handling with the JavaScript “Either” Monad by seppel on Wednesday June 19, 2019 @04:28PM (#20227005)

> That being said, I don't think it takes that much energy to remember that the right is the good value.

And then clever guys come and use left as the good value, because then want to retry on error (as you can see in this thread). Plus it takes quite some energy to discuss the, well, unfortunate naming.

[ Parent | on HN ]

Re:Elegant Error Handling with the JavaScript “Either” Monad by leshow on Wednesday June 19, 2019 @06:30PM (#20228000)

I'm not sure which definition you're referring to, but every one I've seen you'd be hard-pressed to use left as the 'good' value. The type's definition favours 'right' for Functor/Applicative/Monad/etc instances.

[ Parent | on HN ]

Re:Elegant Error Handling with the JavaScript “Either” Monad by seppel on Wednesday June 19, 2019 @07:05PM (#20228230)

I'm referring to this comment: https://news.ycombinator.com/item?id=20224097

[ Parent | on HN ]

Re:Elegant Error Handling with the JavaScript “Either” Monad by leshow on Wednesday June 19, 2019 @07:09PM (#20228253)

There are zero implementations of Left being the Ok value, just this hypothetical put forward by another commenter.

edit: I should specify that I mean when Either is used as a 'Result' type. There are plenty of other use cases you can use Either outside of Ok/Err values.

[ Parent | on HN ]