>That pattern just turns out to be very useful.
Like NaN, it can be hard to track down where things went wrong.
Like NaN, it can be hard to track down where things went wrong.
This is a great reason to avoid huge chunks of code stitched together staying inside Maybe, while still being convenient on the small scale.
Unlike NaN, you have the freedom to not use it when you don't want it.
data Employee = Employee { name : Text, spouse : Maybe Text }
You may also want to use Either to store two possible outcomes of an operation, though I would recommend using your own sum type for clarity: data MyOwnEither a b = MyLeft a | MyRight b