Maybe monad vs exceptions

Question

I wonder what are the advantages of Maybe monad over exceptions? It looks like Maybe is just explicit (and rather space-consuming) way of try..catch syntax.

update Please note that I'm intentionally not mentioning Haskell.

Answer 1

Using Maybe (or its cousin Either which works basically the same way but lets you return an arbitrary value in place of Nothing) serves a slightly different purpose than exceptions. In Java terms, it's like having a checked exception rather than a runtime exception. It represents something expected which you have to deal with, rather than an error you did not expect.

So a function like indexOf would return a Maybe value because you expect the possibility that the item is not in the list. This is much like returning null from a function, except in a type-safe way which forces you to deal with the null case. Either works the same way except that you can return information associated with the error case, so it's actually more similar to an exception than Maybe.

So what are the advantages of the Maybe/Either approach? For one, it's a first-class citizen of the language. Let's compare a function using Either to one throwing an exception. For the exception case, your only real recourse is a try...catch statement. For the Either function, you could use existing combinators to make the flow control clearer. Here are a couple of examples:

First, let's say you want to try several functions that could error out in a row until you get one that doesn't. If you don't get any without errors, you want to return a special error message. This is actually a very useful pattern but would be a horrible pain using try...catch. Happily, since Either is just a normal value, you can use existing functions to make the code much clearer:

firstThing <|> secondThing <|> throwError (SomeError "error message")

Another example is having an optional function. Let's say you have several functions to run, including one that tries to optimize a query. If this fails, you want everything else to run anyhow. You could write code something like:

do a <- getA
   b <- getB
   optional (optimize query)
   execute query a b

Both of these cases are clearer and shorter than using try..catch, and, more importantly, more semantic. Using a function like <|> or optional makes your intentions much clearer than using try...catch to always handle exceptions.

Also note that you do not have to litter your code with lines like if a == Nothing then Nothing else ...! The whole point of treating Maybe and Either as a monad is to avoid this. You can encode the propagation semantics into the bind function so you get the null/error checks for free. The only time you have to check explicitly is if you want to return something other than Nothing given a Nothing, and even then it's easy: there are a bunch of standard library functions to make that code nicer.

Finally, another advantage is that a Maybe/Either type is just simpler. There is no need to extend the language with additional keywords or control structures--everything is just a library. Since they're just normal values, it makes the type system simpler--in Java, you have to differentiate between types (e.g. the return type) and effects (e.g. throws statements) where you wouldn't using Maybe. They also behave just like any other user-defined type--there is no need to have special error-handling code baked into the language.

Another win is that Maybe/Either are functors and monads, which means they can take advantage of the existing monad control flow functions (of which there is a fair number) and, in general, play nicely along with other monads.

That said, there are some caveats. For one, neither Maybe nor Either replace unchecked exceptions. You'll want some other way to handle things like dividing by 0 simply because it would be a pain to have every single division return a Maybe value.

Another problem is having multiple types of errors return (this only applies to Either). With exceptions, you can throw any different types of exceptions in the same function. with Either, you only get one type. This can be overcome with sub-typing or an ADT containing all the different types of errors as constructors (this second approach is what is usually used in Haskell).

Still, over all, I prefer the Maybe/Either approach because I find it simpler and more flexible.

Answer 2

1. An exception can carry more information about the source of a problem. OpenFile() can throw FileNotFound or NoPermission or TooManyDescriptors etc. A None does not carry this information.
2. Exceptions can be used in contexts that lack return values (e.g. with constructors in languages that have them).
3. An exception allows you to very easily send the information up the stack, without a lot of if None return None-style statements.
4. Exception handling almost always carries higher performance impact than just returning a value.

5. Most importantly of all, an exception and a Maybe monad have different purposes - an exception is used to signify a problem, while a Maybe isn't.

   "Nurse, if there's a patient in room 5, can you ask him to wait?"

   • Maybe monad: "Doctor, there is no patient in room 5."
   • Exception: "Doctor, there is no room 5!"

   (notice the "if" - this means the doctor is expecting a Maybe monad)

Answer 3

"Maybe" is not a replacement for exceptions. Exceptions are meant to be used in exceptional cases (for instance: opening a db connection and the db server is not there although it should be). "Maybe" is for modeling a situation when you may or may not have a valid value; say you are getting a value from a dictionary for a key: it may be there or may be not - there is nothing "exceptional" about any of these outcomes.

Answer 4

The maybe monad is basically the same as most mainstream language's use of "null means error" checking (except it requires the null to be checked), and has largely the same advantages and disadvantages.

Answer 5

The Haskell type system will require the user to acknowledge the possibility of a Nothing, whereas programming languages often don't require that an exception be caught. That means that we'll know, at compile-time, that the user has checked for an error.