# What a Monad is not

### From HaskellWiki

(→Monads are not about state: examples for non-state monads) |
|||

(22 intermediate revisions by 6 users not shown) | |||

Line 11: | Line 11: | ||

==Haskell doesn't need Monads== |
==Haskell doesn't need Monads== |
||

− | ...well, apart from the Haskell standard defining the way IO is done in terms of Monads: It could be done differently and still work. |
+ | ...well, apart from the current Haskell standard defining the way IO is done in terms of Monads: It could be done differently and still work. |

==Monads are not impure== |
==Monads are not impure== |
||

Line 17: | Line 17: | ||

==Monads are not about state== |
==Monads are not about state== |
||

− | While it is certainly possible to abstract away explicit state passing by using a Monad, that's not what a monad is. |
+ | While it is certainly possible to abstract away explicit state passing by using a Monad, that's not what a monad is. Some examples for monads that are not about state: Identity monad, Reader monad, List monad, Continuation monad, Exception monad. |

− | |||

− | (some elaboration needed) |
||

==Monads are not about strictness== |
==Monads are not about strictness== |
||

− | Monad operations (bind and return) have to be [[Non-strict semantics|lazy]] in fact, always! However |
+ | Monad operations (bind and return) have to be [[Non-strict semantics|non-strict]] in fact, always! However |

other operations can be specific to each monad. |
other operations can be specific to each monad. |
||

− | For instance some are strict (like IO), and some are lazy (like []). Then there are some that come in multiple flavours, like State. |
+ | For instance some are strict (like IO), and some are non-strict (like []). Then there are some that come in multiple flavours, like State. |

+ | |||

+ | Try the following: |
||

+ | |||

+ | <haskell> |
||

+ | runState (sequence . repeat $ state (\x -> (x,x+1))) 0 |
||

+ | </haskell> |
||

+ | |||

+ | Having a look at the implementation of fixIO might be helpful, too. |
||

==Monads are not values== |
==Monads are not values== |
||

This point might be driven home best by pointing out that instance Monad Foo where ... is not a data type, but a declaration of a typeclass instance. However, to elaborate: |
This point might be driven home best by pointing out that instance Monad Foo where ... is not a data type, but a declaration of a typeclass instance. However, to elaborate: |
||

− | Monads are not values in the same sense that addition and multiplication are not numbers: They capture a -- very specific -- relationship between values of a specific domain into a common abstraction. We're going to call these values monads manage ''mobits'', somewhat like this: |
+ | Monads are not values in the same sense that addition and multiplication are not numbers, or, for that matter, an oven is not food: They capture a -- very specific -- relationship between values of a specific domain into a common abstraction. We're going to call these values monads manage ''mobits'', somewhat like this: |

<haskell> |
<haskell> |
||

Line 39: | Line 39: | ||

The Reader monads manages mobits that are pure computations that use asks to propagate information instead of explicit arguments |
The Reader monads manages mobits that are pure computations that use asks to propagate information instead of explicit arguments |
||

− | ...and while addition and multiplication are both monoids over the positive natural numbers, a monad is a monoid object in a category of endofunctors: return is the unit, and join is the binary operation. It couldn't be more simple. If that confuses you, it might be helpful to see a Monad as a lax functor from a terminal bicategory. |
+ | ...and while addition and multiplication are both monoids over the positive natural numbers, an oven is a monoid over food (Burned pizza doesn't concern us, here: Food stays food, even if you don't want to eat it.), a monad is a monoid object in a category of endofunctors: return is the unit, and join is the binary operation. It couldn't be more simple. If that confuses you, it might be helpful to see a Monad as a lax functor from a terminal bicategory. |

− | |||

− | |||

==Monads are not a replacement for applicative functors== |
==Monads are not a replacement for applicative functors== |
||

Instead, every monad ''is'' an applicative functor (as well as a functor). It is considered good practice not to use >>= if all you need is <*>, or even fmap. |
Instead, every monad ''is'' an applicative functor (as well as a functor). It is considered good practice not to use >>= if all you need is <*>, or even fmap. |
||

− | Not confusing which features of monads are specific to monads only and which stem from applicative functors is vitally important for a deeper understanding of monads. As an example, the applicative functor interface of parser libraries can parse context-free grammars (and look just like EBNF), while the monadic interface can parse context-sensitive grammars: Monads allow you to influence further processing by inspecting the result of your parse. To understand why, have a look at the type of >>=. To understand why applicative functors by themselves are sufficient to track the current parsing position, have a look at the uu-parsinglib tutorial. |
+ | Not confusing which features of monads are specific to monads only and which stem from applicative functors is vitally important for a deeper understanding of monads. As an example, the applicative functor interface of parser libraries can parse context-free grammars (and look just like EBNF), while the monadic interface can parse context-sensitive grammars: Monads allow you to influence further processing by inspecting the result of your parse. To understand why, have a look at the type of >>=. To understand why applicative functors by themselves are sufficient to track the current parsing position, have a look at the [http://www.cs.uu.nl/research/techreps/repo/CS-2008/2008-044.pdf uu-parsinglib tutorial (pdf)]. |

The exact differences are elaborated in even greater detail in Brent Yorgey's excellent [[Typeclassopedia]]. |
The exact differences are elaborated in even greater detail in Brent Yorgey's excellent [[Typeclassopedia]]. |
||

Line 51: | Line 51: | ||

Monads are commonly used to order sequences of computations. But this is misleading. Just as you can use monads for state, or strictness, you can use them to order computations. But there are also commutative monads, like Maybe, that don't order anything. So ordering is not in any way essential to what a monad is. |
Monads are commonly used to order sequences of computations. But this is misleading. Just as you can use monads for state, or strictness, you can use them to order computations. But there are also commutative monads, like Maybe, that don't order anything. So ordering is not in any way essential to what a monad is. |
||

− | I'll try to explain what's meant by ordering. Consider an expression like |
+ | Let's have a look at what's meant by ordering. Consider an expression like |

<haskell> |
<haskell> |
||

− | let x = a |
+ | let x = a |

− | y = b |
+ | y = b |

− | in f x y |
+ | in f x y |

</haskell> |
</haskell> |
||

Line 62: | Line 62: | ||

<haskell> |
<haskell> |
||

− | let y = b |
+ | let y = b |

− | x = a |
+ | x = a |

− | in f x y |
+ | in f x y |

</haskell> |
</haskell> |
||

− | It doesn't matter what order we write the two assignments. But for doing I/O we'd like ordering. Monads allow use to express |
+ | It doesn't matter what order we write the two bindings. But for doing I/O we'd like ordering. Monads allow us to express |

<haskell> |
<haskell> |
||

− | do |
+ | do |

− | x <- getChar |
+ | x <- getChar |

− | y <- getChar |
+ | y <- getChar |

− | return (x,y) |
+ | return (x,y) |

</haskell> |
</haskell> |
||

Line 79: | Line 79: | ||

<haskell> |
<haskell> |
||

− | do |
+ | do |

− | y <- getChar |
+ | y <- getChar |

− | x <- getChar |
+ | x <- getChar |

− | return (x,y) |
+ | return (x,y) |

</haskell> |
</haskell> |
||

− | The second example returns a pair of characters in the opposite order to which they were entered. |
+ | Unlike the first, the second example returns a pair of characters in the opposite order to which they were entered. |

− | However, there are monads for which swapping the order of lines like this makes no difference. For example the Maybe monad. |
+ | It might help to meditate about the difference between 'assignment' and 'binding', right now. |

+ | |||

+ | However, just to spoil the enlightenment you just attained, there are monads for which swapping the order of lines like this makes no difference: For example, the Maybe monad. |
||

So while it is correct to say that monads can be used to order operations, it would be wrong to say that monads are a mechanism for ordering operations. |
So while it is correct to say that monads can be used to order operations, it would be wrong to say that monads are a mechanism for ordering operations. |
||

− | This notion of commutativity is different from the familiar the one in algebra where a+b=b+a. So it's not about the fact that |
+ | This notion of commutativity looks superficially very different from the familiar one in vanilla algebra where a+b=b+a. It's not about the fact that |

<haskell> |
<haskell> |
||

− | (Just 2 >> Just 3) == Just 3 |
+ | (Just 2 >> Just 3) == Just 3 |

+ | </haskell> |
||

+ | , implying |
||

+ | <haskell> |
||

+ | (Just 2 >> Just 3) /= (Just 3 >> Just 2) |
||

</haskell> |
</haskell> |
||

− | (It took long to explain that, maybe someone can edit this down.) |
+ | This shouldn't be too surprising, though, as >> isn't the binary operation of some monoid: the algebraic properties of '''''join''''' are very close to those of + and incidentally, '''''join''''' is also the operation true category theorists tend to work with. They also know of bind, but don't use it a lot because, unlike programmers, they don't do any actual productive work. |

==See also== |
==See also== |

## Revision as of 14:18, 5 January 2012

## 1 Warning

This page is currently an unprocessed braindump. Feel free to dump additional stuff or massage stuff into didactic pleasures.

Also, don't be surprised if you leave this page more confused than before. That just means that it has successfully destroyed your false assumptions, or that you've fallen for some horrible inside joke. Beware of Zygohistomorphic prepromorphisms. Go for warm and fuzzy, instead.

## 2 Monads are not a good choice as topic for your first Haskell blog entry

...just accept that they're burritos, and wait until later.

## 3 Monads are not a language feature

Really. They are defined in terms of Haskell, not Haskell in terms of them. Conversely,

## 4 Haskell doesn't need Monads

...well, apart from the current Haskell standard defining the way IO is done in terms of Monads: It could be done differently and still work.

## 5 Monads are not impure

...In no way whatsoever. You don't even need flexible morals to claim it. To be more specific, it's IO that's impure. That makes the IO monad impure. But that's not a general property of monads - just IO. And even then, we can pretend that Haskell is a purely functional description language for imperative programs. But we didn't want to employ flexible morals, now did we?

## 6 Monads are not about state

While it is certainly possible to abstract away explicit state passing by using a Monad, that's not what a monad is. Some examples for monads that are not about state: Identity monad, Reader monad, List monad, Continuation monad, Exception monad.

## 7 Monads are not about strictness

Monad operations (bind and return) have to be non-strict in fact, always! However other operations can be specific to each monad. For instance some are strict (like IO), and some are non-strict (like []). Then there are some that come in multiple flavours, like State.

Try the following:

runState (sequence . repeat $ state (\x -> (x,x+1))) 0

Having a look at the implementation of fixIO might be helpful, too.

## 8 Monads are not values

This point might be driven home best by pointing out that instance Monad Foo where ... is not a data type, but a declaration of a typeclass instance. However, to elaborate:

Monads are not values in the same sense that addition and multiplication are not numbers, or, for that matter, an oven is not food: They capture a -- very specific -- relationship between values of a specific domain into a common abstraction. We're going to call these values monads manage *mobits*, somewhat like this:

type Mobit m a = Monad m => m a

The IO monad manages mobits representing side-effects ("IO actions").

The List monad manages mobits representing multiple values ("[a]")

The Reader monads manages mobits that are pure computations that use asks to propagate information instead of explicit arguments

...and while addition and multiplication are both monoids over the positive natural numbers, an oven is a monoid over food (Burned pizza doesn't concern us, here: Food stays food, even if you don't want to eat it.), a monad is a monoid object in a category of endofunctors: return is the unit, and join is the binary operation. It couldn't be more simple. If that confuses you, it might be helpful to see a Monad as a lax functor from a terminal bicategory.

## 9 Monads are not a replacement for applicative functors

Instead, every monad *is* an applicative functor (as well as a functor). It is considered good practice not to use >>= if all you need is <*>, or even fmap.

Not confusing which features of monads are specific to monads only and which stem from applicative functors is vitally important for a deeper understanding of monads. As an example, the applicative functor interface of parser libraries can parse context-free grammars (and look just like EBNF), while the monadic interface can parse context-sensitive grammars: Monads allow you to influence further processing by inspecting the result of your parse. To understand why, have a look at the type of >>=. To understand why applicative functors by themselves are sufficient to track the current parsing position, have a look at the uu-parsinglib tutorial (pdf).

The exact differences are elaborated in even greater detail in Brent Yorgey's excellent Typeclassopedia.

## 10 Monads are not about ordering/sequencing

Monads are commonly used to order sequences of computations. But this is misleading. Just as you can use monads for state, or strictness, you can use them to order computations. But there are also commutative monads, like Maybe, that don't order anything. So ordering is not in any way essential to what a monad is.

Let's have a look at what's meant by ordering. Consider an expression like

let x = a y = b in f x y

That gives the same result as

let y = b x = a in f x y

It doesn't matter what order we write the two bindings. But for doing I/O we'd like ordering. Monads allow us to express

do x <- getChar y <- getChar return (x,y)

and have it be different from

do y <- getChar x <- getChar return (x,y)

Unlike the first, the second example returns a pair of characters in the opposite order to which they were entered.

It might help to meditate about the difference between 'assignment' and 'binding', right now.

However, just to spoil the enlightenment you just attained, there are monads for which swapping the order of lines like this makes no difference: For example, the Maybe monad.

So while it is correct to say that monads can be used to order operations, it would be wrong to say that monads are a mechanism for ordering operations.

This notion of commutativity looks superficially very different from the familiar one in vanilla algebra where a+b=b+a. It's not about the fact that

(Just 2 >> Just 3) == Just 3

, implying

(Just 2 >> Just 3) /= (Just 3 >> Just 2)

This shouldn't be too surprising, though, as >> isn't the binary operation of some monoid: the algebraic properties of * join* are very close to those of + and incidentally,

*is also the operation true category theorists tend to work with. They also know of bind, but don't use it a lot because, unlike programmers, they don't do any actual productive work.*

**join**