4 ms·
> That's about as easy it gets when it comes to remembering things I use a statically typed language so I have fewer things to remember because the compiler do
by hota_mazi 9y ago
> That's about as easy it gets when it comes to remembering things
I use a statically typed language so I have fewer things to remember because the compiler does the bookkeeping for me.
`Either` is a generic variant record, it should not be used to carry errors.
And as a general rule, any programming construct that relies on convention instead of static typing is prone to generating bugs.
- taeric 9y agoTo be fair, this is more relying on a pun than it is convention. I don't think this changes your point, though.
- nemetroid 9y ago> `Either` is a generic variant record, it should not be used to carry errors. The name suggests that, but the Monad instance suggests that Either is an asymmetric data type, where the left and right branches carry different meaning. > And as a general rule, any programming construct that relies on convention instead of static typing is prone to generating bugs. If the Either branches were named `Error` and `Success`, using `Error` to carry errors would be just as much of a convention as using `Left` for that purpose (a more sensible convention, but nonetheless a convention). The only way you'd get around that is if you'd somehow encode in the language what is and what isn't an error and use that to statically force correct branch usage.