int
@@ 74,8 +70,8 @@ A lot of what we'll be doing concerns types that are called *Kleisli arrows*. Do
P > Q
That is, they are functions from values of one type `P` to a boxed type `Q`, for some choice of type expressions `P` and `Q`.
For instance, the following are Kleisli arrows:
+That is, they are functions from values of one type `P` to a boxed type `Q`, for some choice of box and of type expressions `P` and `Q`.
+For instance, the following are Kleisli arrow types:
int > bool
@@ 83,12 +79,25 @@ For instance, the following are Kleisli arrows:
In the first, `P` has become `int` and `Q` has become `bool`. (The boxed type Q
is bool
).
Note that the lefthand schema `P` is permitted to itself be a boxed type. That is, where
if `Î± list` is our box type, we can write the second type as:
+Note that either of the schemas `P` or `Q` are permitted to themselves be boxed
+types. That is, if `Î± list` is our box type, we can write the second type as:
int > int list
As semanticists, you are no doubt familiar with the debates between those who insist that propositions are sets of worlds and those who insist they are context change potentials. We hope to show you, in coming weeks, that propositions are (certain sorts of) Kleisli arrows. But this doesn't really compete with the other proposals; it is a generalization of them. Both of the other proposed structures can be construed as specific Kleisli arrows.
+And also what the rhs there is a boxing of is itself a boxed type (with the same kind of box):, so we can write it as:
+
+int > int
+
+We have to be careful though not to to unthinkingly equivocate between different kinds of boxes.
+
+Here are some examples of values of these Kleisli arrow types, where the box type is `Î± list`, and the Kleisli arrow types are int > int
(that is, `int > int list`) or int > bool
:
+
+\x. [x] +\x. [odd? x, odd? x] +\x. prime_factors_of x +\x. [0, 0, 0]+ +As semanticists, you are no doubt familiar with the debates between those who insist that propositions are sets of worlds and those who insist they are context change potentials. We hope to show you, in coming weeks, that propositions are (certain sorts of) Kleisli arrows. But this [doesn't really compete](/images/faye_dunaway.jpg) with the other proposals; it is a generalization of them. Both of the other proposed structures can be construed as specific Kleisli arrow types. ## A family of functions for each box type ## @@ 99,88 +108,200 @@ Here are the types of our crucial functions, together with our pronunciation, an
map (/mÃ¦p/): (P > Q) > P > Q
+> In Haskell, this is the function `fmap` from the `Prelude` and `Data.Functor`; also called `<$>` in `Data.Functor` and `Control.Applicative`, and also called `Control.Applicative.liftA` and `Control.Monad.liftM`.
+
map2 (/mÃ¦ptu/): (P > Q > R) > P > Q > R
mid (/ÎµmaidÎµnt@tI/ aka unit, return, pure): P > P
+> In Haskell, this is called `Control.Applicative.liftA2` and `Control.Monad.liftM2`.
m$ or mapply (/Îµm@plai/): P > Q > P > Q
+â§ or mid (/ÎµmaidÎµnt@tI/): P > P
<=< or mcomp : (Q > R) > (P > Q) > (P > R)
+> This notion is exemplified by `Just` for the box type `Maybe Î±` and by the singleton function for the box type `List Î±`. It will be a way of boxing values with your box type that plays a distinguished role in the various Laws and interdefinitions we present below.
>=> (flip mcomp, should we call it mpmoc?): (P > Q) > (Q > R) > (P > R)
+> In Haskell, this is called `Control.Monad.return` and `Control.Applicative.pure`. In other theoretical contexts it is sometimes called `unit` or `Î·`. All of these names are somewhat unfortunate. First, it has little to do with `Î·`reduction in the Lambda Calculus. Second, it has little to do with the `() : unit` value we discussed in earlier classes. Third, it has little to do with the `return` keyword in C and other languages; that's more closely related to continuations, which we'll discuss in later weeks. Finally, this doesn't perfectly align with other uses of "pure" in the literature. `â§`'d values _will_ generally be "pure" in the other senses, but other boxed values can be too.
>>= or mbind : (Q) > (Q > R) > (R)
+> For all these reasons, we're thinking it will be clearer in our discussion to use a different name. In the class presentation Jim called it `ð`; and in an earlier draft of this page we (only) called it `mid` ("m" plus "identity"); but now we're trying out `â§` as a symbolic alternative. But in the end, we might switch to just using `Î·`.
=<< (flip mbind, should we call it mdnib?) (Q > R) > (Q) > (R)
+Â¢ or mapply (/Îµm@plai/): P > Q > P > Q
join: P > P
+> We'll use `Â¢` as a leftassociative infix operator, reminiscent of (the rightassociative) `$` which is just ordinary function application (also expressed by mere leftassociative juxtaposition). In the class presentation Jim called `Â¢` `â«`; and in an earlier draft of this page we called it `m$`. In Haskell, it's called `Control.Monad.ap` or `Control.Applicative.<*>`.
+<=< or mcomp : (Q > R) > (P > Q) > (P > R)
In the class handout, we gave the types for `>=>` twice, and once was correct but the other was a typo. The above is the correct typing.

Also, in the handout we called `mid` `ð`. But now we've decided that `mid`
is better. (Think of it as "m" plus "identity", not as the start of "midway".)
+> In Haskell, this is `Control.Monad.<=<`.
The menagerie isn't quite as bewildering as you might suppose. Many of these will
be interdefinable. For example, here is how `mcomp` and `mbind` are related: k <=< j â¡
\a. (j a >>= k)
.
+>=> or flip mcomp : (P > Q) > (Q > R) > (P > R)
We will move freely back and forth between using `>=>` and using `<=<` (aka `mcomp`), which
is just `>=>` with its arguments flipped. `<=<` has the virtue that it corresponds more
+> In Haskell, this is `Control.Monad.>=>`. We will move freely back and forth between using `<=<` (aka `mcomp`) and using `>=>`, which
+is just `<=<` with its arguments flipped. `<=<` has the virtue that it corresponds more
closely to the ordinary mathematical symbol `â`. But `>=>` has the virtue
that its types flow more naturally from left to right.
+> In the class handout, we gave the types for `>=>` twice, and once was correct but the other was a typo. The above is the correct typing.
+
+>>= or mbind : (Q) > (Q > R) > (R)
+
+> Haskell uses the symbol `>>=` but calls it "bind". This is not well chosen from the perspective of formal semantics, since it's only loosely connected with what we mean by "binding." But the name is too deeply entrenched to change. We've at least preprended an "m" to the front of "bind". In some presentations this operation is called `â
`.
+
+=<< or flip mbind : (Q > R) > (Q) > (R)
+
+join: P > P
+
+> In Haskell, this is `Control.Monad.join`. In other theoretical contexts it is sometimes called `Î¼`.
+
+The menagerie isn't quite as bewildering as you might suppose. Many of these will be interdefinable. For example, here is how `mcomp` and `mbind` are related: k <=< j â¡ \a. (j a >>= k)
. We'll state some other interdefinitions below.
+
These functions come together in several systems, and have to be defined in a way that coheres with the other functions in the system:
* ***Mappable*** (in Haskelese, "Functors") At the most general level, box types are *Mappable*
if there is a `map` function defined for that box type with the type given above. This
has to obey the following Map Laws:
 map (id : Î± > Î±) = (id : Î± > Î±)
 map (g â f) = (map g) â (map f)
+ map (id : Î± > Î±) == (id : Î± > Î±)
+ map (g â f) == (map g) â (map f)
Essentially these say that `map` is a homomorphism from the algebra of `(universe Î± > Î², operation â, elsment id)` to that of (Î± > Î², â', id')
, where `â'` and `id'` are `â` and `id` restricted to arguments of type _
. That might be hard to digest because it's so abstract. Think of the following concrete example: if you take a `Î± list` (that's our Î±
), and apply `id` to each of its elements, that's the same as applying `id` to the list itself. That's the first law. And if you apply the composition of functions `g â f` to each of the list's elements, that's the same as first applying `f` to each of the elements, and then going through the elements of the resulting list and applying `g` to each of those elements. That's the second law. These laws obviously hold for our familiar notion of `map` in relation to lists.
 > As mentioned at the top of the page, in Category Theory presentations of monads they usually talk about "endofunctors", which are mappings from a Category to itself. In the uses they make of this notion, the endofunctors combine the role of a box type _
and of the `map` that goes together with it.
+ > As mentioned at the top of the page, in Category Theory presentations of monads they usually talk about "endofunctors", which are mappings from a Category to itself. In the uses they make of this notion, the endofunctors combine the role of a box type _
and of the `map` that goes together with it.
* ***MapNable*** (in Haskelese, "Applicatives") A Mappable box type is *MapNable*
 if there are in addition `map2`, `mid`, and `mapply`. (Given either
+ if there are in addition `map2`, `â§`, and `mapply`. (Given either
of `map2` and `mapply`, you can define the other, and also `map`.
Moreover, with `map2` in hand, `map3`, `map4`, ... `mapN` are easily definable.) These
have to obey the following MapN Laws:
 TODO LAWS
+ 1. â§(id : P>P) : P > P
is a left identity for `Â¢`, that is: `(â§id) Â¢ xs = xs`
+ 2. `â§(f a) = (â§f) Â¢ (â§a)`
+ 3. The `map2`ing of composition onto boxes `fs` and `gs` of functions, when `Â¢`'d to a box `xs` of arguments == the `Â¢`ing of `fs` to the `Â¢`ing of `gs` to xs: `(â§(â) Â¢ fs Â¢ gs) Â¢ xs = fs Â¢ (gs Â¢ xs)`.
+ 4. When the arguments (the righthand operand of `Â¢`) are an `â§`'d value, the order of `Â¢`ing doesn't matter: `fs Â¢ (â§x) = â§($x) Â¢ fs`. (Though note that it's `â§($x)`, or `â§(\f. f x)` that gets `Â¢`d onto `fs`, not the original `â§x`.) Here's an example where the order *does* matter: `[succ,pred] Â¢ [1,2] == [2,3,0,1]`, but `[($1),($2)] Â¢ [succ,pred] == [2,0,3,1]`. This Law states a class of cases where the order is guaranteed not to matter.
+ 5. A consequence of the laws already stated is that when the _left_hand operand of `Â¢` is a `â§`'d value, the order of `Â¢`ing doesn't matter either: `â§f Â¢ xs == map (flip ($)) xs Â¢ â§f`.
+
+
+
+* ***Monad*** (or "Composables") A MapNable box type is a *Monad* if there
+ is in addition an associative `mcomp` having `â§` as its left and
+ right identity. That is, the following Monad Laws must hold:
+ mcomp (mcomp j k) l (that is, (j <=< k) <=< l) == mcomp j (mcomp k l)
+ mcomp mid k (that is, â§ <=< k) == k
+ mcomp k mid (that is, k <=< â§) == k
* ***Monad*** (or "Composables") A MapNable box type is a *Monad* if there
 is in addition an associative `mcomp` having `mid` as its left and
 right identity. That is, the following Monad Laws must hold:
+ You could just as well express the Monad laws using `>=>`:
+
+ l >=> (k >=> j) == (l >=> k) >=> j
+ k >=> â§ == k
+ â§ >=> k == k
+
+ If you studied algebra, you'll remember that a mon*oid* is a universe with some associative operation that has an identity. For example, the natural numbers form a monoid with multiplication as the operation and `1` as the identity, or with addition as the operation and `0` as the identity. Strings form a monoid with concatenation as the operation and the empty string as the identity. (This example shows that the operation need not be commutative.) Monads are a kind of generalization of this notion, and that's why they're named as they are. The key difference is that for monads, the values being operated on need not be of the same type. They *can* be, if they're all Kleisli arrows of a single type P > P
. But they needn't be. Their types only need to "cohere" in the sense that the output type of the one arrow is a boxing of the input type of the next.
+
+ In the Haskell manuals, they express the Monad Laws using `>>=` instead of the composition operators `>=>` or `<=<`. This looks similar, but doesn't have the same symmetry:
+
+ u >>= (\a > k a >>= j) == (u >>= k) >>= j
+ u >>= â§ == u
+ â§a >>= k == k a
+
+ (Also, Haskell calls `â§` `return` or `pure`, but we've stuck to our terminology in this context.) Some authors try to make the first of those Laws look more symmetrical by writing it as:
 mcomp (mcomp j k) l (that is, (j <=< k) <=< l) = mcomp j (mcomp k l)
 mcomp mid k (that is, mid <=< k) = k
 mcomp k mid (that is, k <=< mid) = k
+ (A >>= \a > B) >>= \b > C == A >>= (\a > B >>= \b > C)
If you have any of `mcomp`, `mpmoc`, `mbind`, or `join`, you can use them to define the others.
Also, with these functions you can define `m$` and `map2` from *MapNables*. So all you really need
are a definition of `mid`, on the one hand, and one of `mcomp`, `mbind`, or `join`, on the other.
+ If you have any of `mcomp`, `mpmoc`, `mbind`, or `join`, you can use them to define the others. Also, with these functions you can define `Â¢` and `map2` from *MapNables*. So with Monads, all you really need to get the whole system of functions are a definition of `â§`, on the one hand, and one of `mcomp`, `mbind`, or `join`, on the other.
Here are some interdefinitions: TODO
Names in Haskell: TODO
+ > In Category Theory discussion, the Monad Laws are instead expressed in terms of `join` (which they call `Î¼`) and `â§` (which they call `Î·`). These are assumed to be "natural transformations" for their box type, which means that they satisfy these equations with that box type's `map`:
+ > map f â â§ == â§ â f+ > The Monad Laws then take the form: + >
map f â join == join â map (map f)
join â (map join) == join â join+ > The first of these says that if you have a triplyboxed type, and you first merge the inner two boxes (with `map join`), and then merge the resulting box with the outermost box, that's the same as if you had first merged the outer two boxes, and then merged the resulting box with the innermost box. The second law says that if you take a box type and wrap a second box around it (with `â§`) and then merge them, that's the same as if you had done nothing, or if you had instead wrapped a second box around each element of the original (with `map â§`, leaving the original box on the outside), and then merged them.
join â â§ == id == join â map â§
+ > The Category Theorist would state these Laws like this, where `M` is the endofunctor that takes us from type `Î±` to type Î±
:
+ >
Î¼ â M(Î¼) == Î¼ â Î¼+ > A word of advice: if you're doing any work in this conceptual neighborhood and need a Greek letter, don't use Î¼. In addition to the preceding usage, there's also a use in recursion theory (for the minimization operator), in type theory (as a fixed point operator for types), and in the Î»Î¼calculus, which is a formal system that deals with _continuations_, which we will focus on later in the course. So Î¼ already exhibits more ambiguity than it can handle. + > We link to further reading about the Category Theory origins of Monads below. + +There isn't any single `â§` function, or single `mbind` function, and so on. For each new box type, this has to be worked out in a useful way. And as we hinted, in many cases the choice of box *type* still leaves some latitude about how they should be defined. We commonly talk about "the List Monad" to mean a combination of the choice of `Î± list` for the box type and particular definitions for the various functions listed above. There's also "the ZipList MapNable/Applicative" which combines that same box type with other choices for (some of) the functions. Many of these packages also define specialpurpose operations that only make sense for that system, but not for other Monads or Mappables. + +As hinted in last week's homework and explained in class, the operations available in a Mappable system exactly preserve the "structure" of the boxed type they're operating on, and moreover are only sensitive to what content is in the corresponding original position. If you say `map f [1,2,3]`, then what ends up in the first position of the result depends only on how `f` and `1` combine. + +For MapNable operations, on the other hand, the structure of the result may instead be a complex function of the structure of the original arguments. But only of their structure, not of their contents. And if you say `map2 f [10,20] [1,2,3]`, what ends up in the first position of the result depends only on how `f` and `10` and `1` combine. + +With `map`, you can supply an `f` such that `map f [3,2,0,1] == [[3,3,3],[2,2],[],[1]]`. But you can't transform `[3,2,0,1]` to `[3,3,3,2,2,1]`, and you can't do that with MapNable operations, either. That would involve the structure of the result (here, the length of the list) being sensitive to the content, and not merely the structure, of the original. + +For Monads (Composables), on the other hand, you can perform more radical transformations of that sort. For example, `join (map (\x. dup x x) [3,2,0,1])` would give us `[3,3,3,2,2,1]` (for a suitable definition of `dup`). + + + + +## Interdefinitions and Subsidiary notions## + +We said above that various of these box type operations can be defined in terms of others. Here is a list of various ways in which they're related. We try to stick to the consistent typing conventions that: + +
Î¼ â Î· == id == Î¼ â M(Î·)
+f : Î± > Î²; g and h have types of the same form
+ also sometimes these will have types of the form Î± > Î² > Î³
+ note that Î± and Î² are permitted to be, but needn't be, boxed types
+j : Î± > Î²; k and l have types of the same form
+u : Î±; v and xs and ys have types of the same form
+
+w : Î±
+
+
+But we may sometimes slip.
+
+Here are some ways the different notions are related:
+
++j >=> k â¡= \a. (j a >>= k) +u >>= k == (id >=> k) u; or ((\(). u) >=> k) () +u >>= k == join (map k u) +join w == w >>= id +map2 f xs ys == xs >>= (\x. ys >>= (\y. â§(f x y))) +map2 f xs ys == (map f xs) Â¢ ys, using Â¢ as an infix operator +fs Â¢ xs == fs >>= (\f. map f xs) +Â¢ == map2 id +map f xs == â§f Â¢ xs +map f u == u >>= â§ â f ++ + +Here are some other monadic notion that you may sometimes encounter: + +*
mzero
is a value of type Î±
that is exemplified by `Nothing` for the box type `Maybe Î±` and by `[]` for the box type `List Î±`. It has the behavior that `anything Â¢ mzero == mzero == mzero Â¢ anything == mzero >>= anything`. In Haskell, this notion is called `Control.Applicative.empty` or `Control.Monad.mzero`.
+
+* Haskell has a notion `>>` definable as `\u v. map (const id) u Â¢ v`, or as `\u v. u >>= const v`. This is often useful, and `u >> v` won't in general be identical to just `v`. For example, using the box type `List Î±`, `[1,2,3] >> [4,5] == [4,5,4,5,4,5]`. But in the special case of `mzero`, it is a consequence of what we said above that `anything >> mzero == mzero`. Haskell also calls `>>` `Control.Applicative.*>`.
+
+* Haskell has a correlative notion `Control.Applicative.<*`, definable as `\u v. map const u Â¢ v`. For example, `[1,2,3] <* [4,5] == [1,1,2,2,3,3]`.
+
+* mapconst
is definable as `map â const`. For example `mapconst 4 [1,2,3] == [4,4,4]`. Haskell calls `mapconst` `<$` in `Data.Functor` and `Control.Applicative`. They also use `$>` for `flip mapconst`, and `Control.Monad.void` for `mapconst ()`.
+
The name "bind" is not well chosen from our perspective, but this is too deeply entrenched by now.
## Examples ##
To take a trivial (but, as we will see, still useful) example,
consider the Identity box type: `Î±`. So if `Î±` is type `bool`,
then a boxed `Î±` is ... a `bool`. That is, Î± = Î±
.
+then a boxed `Î±` is ... a `bool`. That is, Î± == Î±
.
In terms of the box analogy, the Identity box type is a completely invisible box. With the following
definitions:
 mid â¡ \p. p
 mcomp â¡ \f g x.f (g x)
+ mid (* or â§ *) â¡ \p. p, that is, our familiar combinator I
+ mcomp (* or <=< *) â¡ \f g x. f (g x), that is, ordinary function composition (â) (aka the B combinator)
Identity is a monad. Here is a demonstration that the laws hold:
@@ 205,6 +326,10 @@ Identity is a monad. Here is a demonstration that the laws hold:
The Identity monad is favored by mimes.
+
+
+
+
To take a slightly less trivial (and even more useful) example,
consider the box type `Î± list`, with the following operations:
@@ 230,191 +355,115 @@ For example:
`j 7` produced `[49, 14]`, which after being fed through `k` gave us `[49, 50, 14, 15]`.
Contrast that to `m$` (`mapply`, which operates not on two *boxproducing functions*, but instead on two *values of a boxed type*, one containing functions to be applied to the values in the other box, via some predefined scheme. Thus:
+Contrast that to `Â¢` (`mapply`), which operates not on two *boxproducing functions*, but instead on two *boxed type values*, one containing functions to be applied to the values in the other box, via some predefined scheme. Thus:
let js = [(\a>a*a),(\a>a+a)] in
let xs = [7, 5] in
mapply js xs ==> [49, 25, 14, 10]
+These implementations of `<=<` and `Â¢` for lists use the "crossing" strategy for pairing up multiple lists, as opposed to the "zipping" strategy. Nothing forces that choice; you could also define `Â¢` using the "zipping" strategy instead. (But then you wouldn't be able to build a corresponding Monad; see below.) Haskell talks of the List Monad in the first case, and the ZipList Applicative in the second case.
As we illustrated in class, there are clear patterns shared between lists and option types and trees, so perhaps you can see why people want to figure out the general structures. But it probably isn't obvious yet why it would be useful to do so. To a large extent, this will only emerge over the next few classes. But we'll begin to demonstrate the usefulness of these patterns by talking through a simple example, that uses the monadic functions of the Option/Maybe box type.

+Sticking with the "crossing" strategy, here's how to motivate our implementation of `<=<`. Recall that we have on the one hand, an operation `filter` for lists, that applies a predicate to each element of the list, and returns a list containing only those elements which satisfied the predicate. But the elements it does retain, it retains unaltered. On the other hand, we have the operation `map` for lists, that is capable of _changing_ the list elements in the result. But it doesn't have the power to throw list elements away; elements in the source map onetoone to elements in the result. In many cases, we want something in between `filter` and `map`. We want to be able to ignore or discard some list elements, and possibly also to change the list elements we keep. One way of doing this is to have a function `optmap`, defined like this:
## Safe division ##
+ let rec optmap (f : Î± > Î² option) (xs : Î± list) : Î² list =
+ match xs with
+  [] > []
+  x' :: xs' >
+ (match f x' with
+  None > optmap f xs'
+  Some b > b :: optmap f xs')
Integer division presupposes that its second argument
(the divisor) is not zero, upon pain of presupposition failure.
Here's what my OCaml interpreter says:
+Then we retain only those `Î±`s for which `f` returns `Some b`; when `f` returns `None`, we just leave out any corresponding element in the result.
 # 12/0;;
 Exception: Division_by_zero.
+That can be helpful, but it only enables us to have _zero or one_ elements in the result corresponding to a given element in the source list. What if we sometimes want more? Well, here is a more general approach:
Say we want to explicitly allow for the possibility that
division will return something other than a number.
To do that, we'll use OCaml's `option` type, which works like this:
+ let rec catmap (k : Î± > Î² list) (xs : Î± list) : Î² list =
+ match xs with
+  [] > []
+  x' :: xs' > List.append (k x') (catmap k xs')
 # type 'a option = None  Some of 'a;;
 # None;;
  : 'a option = None
 # Some 3;;
  : int option = Some 3
+Now we can have as many elements in the result for a given `Î±` as `k` cares to return. Another way to write `catmap k xs` is as (Haskell) `concat (map k xs)` or (OCaml) `List.flatten (List.map k xs)`. And this is just the definition of `mbind` or `>>=` for the List Monad. The definition of `mcomp` or `<=<`, that we gave above, differs only in that it's the way to compose two functions `j` and `k`, that you'd want to `catmap`, rather than the way to `catmap` one of those functions over a value that's already a list.
So if a division is normal, we return some number, but if the divisor is
zero, we return `None`. As a mnemonic aid, we'll prepend a `safe_` to the start of our new divide function.
+This example is a good intuitive basis for thinking about the notions of `mbind` and `mcomp` more generally. Thus `mbind` for the option/Maybe type takes an option value, applies `k` to its element (if there is one), and returns the resulting option value. `mbind` for a tree with `Î±`labeled leaves would apply `k` to each of the leaves, and return a tree containing arbitrarily large subtrees in place of all its former leaves, depending on what `k` returned.
let safe_div (x:int) (y:int) =  match y with   0 > None   _ > Some (x / y);;  (* val safe_div : int > int > int option = fun # safe_div 12 2;;  : int option = Some 6 # safe_div 12 0;;  : int option = None # safe_div (safe_div 12 2) 3;;  ~~~~~~~~~~~~~ Error: This expression has type int option  but an expression was expected of type int *) +[3, 2, 0, 1] >>=_{Î± list} (\a > dup a a) ==> [3, 3, 3, 2, 2, 1] + + Some a >>=_{Î± option} (\a > Some 0) ==> Some 0 + None >>=_{Î± option} (\a > Some 0) ==> None + Some a >>=_{Î± option} (\a > None ) ==> None + + . + / \ + . / \ + / \ . . \ + . 3 >>=_{(Î±,unit) tree} (\a > / \ ) ==> / \ . + / \ a a / \ / \ +1 2 . . 3 3 + / \ / \ + 1 1 2 2This starts off well: dividing `12` by `2`, no problem; dividing `12` by `0`, just the behavior we were hoping for. But we want to be able to use the output of the safedivision function as input for further division operations. So we have to jack up the types of the inputs: 
let safe_div2 (u:int option) (v:int option) =  match u with   None > None   Some x >  (match v with   Some 0 > None   Some y > Some (x / y));;  (* val safe_div2 : int option > int option > int option =+Though as we warned before, only some of the Monads we'll be working with are naturally thought of "containers"; so in other cases the similarity of their `mbind` operations to what we have here will be more abstract. Calling the function now involves some extra verbosity, but it gives us what we need: now we can try to divide by anything we want, without fear that we're going to trigger system errors. I prefer to line up the `match` alternatives by using OCaml's builtin tuple type: +The question came up in class of **when box types might fail to be Mappable, or Mappables might fail to be MapNables, or MapNables might fail to be Monads**. # safe_div2 (Some 12) (Some 2);;  : int option = Some 6 # safe_div2 (Some 12) (Some 0);;  : int option = None # safe_div2 (safe_div2 (Some 12) (Some 0)) (Some 3);;  : int option = None *) 
let safe_div2 (u:int option) (v:int option) =  match (u, v) with   (None, _) > None   (_, None) > None   (_, Some 0) > None   (Some x, Some y) > Some (x / y);; +For the first failure, we noted that it's easy to define a `map` operation for the box type `R > Î±`, for a fixed type `R`. You `map` a function of type `P > Q` over a value of the boxed type
P
, that is a value of type `R > P`, by just returning a function that takes some `R` as input, first supplies it to your `R > P` value, and then supplies the result to your `map`ped function of type `P > Q`. (We will be working with this Mappable extensively; in fact it's not just a Mappable but more specifically a Monad.)
So far so good. But what if we want to combine division with
other arithmetic operations? We need to make those other operations
aware of the possibility that one of their arguments has already triggered a
presupposition failure:
+But if on the other hand, your box type is `Î± > R`, you'll find that there is no way to define a `map` operation that takes arbitrary functions of type `P > Q` and values of the boxed type P
, that is `P > R`, and returns values of the boxed type Q
.
let safe_add (u:int option) (v:int option) =  match (u, v) with   (None, _) > None   (_, None) > None   (Some x, Some y) > Some (x + y);;  (* val safe_add : int option > int option > int option =+For the second failure, that is cases of Mappables that are not MapNables, we cited box types like `(R, Î±)`, for arbitrary fixed types `R`. The `map` operation for these is defined by `map f (r,a) = (r, f a)`. For certain choices of `R` these can be MapNables too. The easiest case is when `R` is the type of `()`. But when we look at the MapNable Laws, we'll see that they impose constraints we cannot satisfy for *every* choice of the fixed type `R`. Here's why. We'll need to define `â§a = (r0, a)` for some specific `r0` of type `R`. The choice can't depend on the value of `a`, because `â§` needs to work for `a`s of _any_ type. Then the MapNable Laws will entail: This works, but is somewhat disappointing: the `safe_add` operation doesn't trigger any presupposition of its own, so it is a shame that it needs to be adjusted because someone else might make trouble. + 1. (r0,id) Â¢ (r,x) == (r,x) + 2. (r0,f x) == (r0,f) Â¢ (r0,x) + 3. (r0,(â)) Â¢ (r'',f) Â¢ (r',g) Â¢ (r,x) == (r'',f) Â¢ ((r',g) Â¢ (r,x)) + 4. (r'',f) Â¢ (r0,x) == (r0,($x)) Â¢ (r'',f) + 5. (r0,f) Â¢ (r,x) == (r,($x)) Â¢ (r0,f) But we can automate the adjustment, using the monadic machinery we introduced above. As we said, there needs to be different `>>=`, `map2` and so on operations for each monad or box type we're working with. Haskell finesses this by "overloading" the single symbol `>>=`; you can just input that symbol and it will calculate from the context of the surrounding type constraints what monad you must have meant. In OCaml, the monadic operators are not predefined, but we will give you a library that has definitions for all the standard monads, as in Haskell. For now, though, we will define our `>>=` and `map2` operations by hand: +Now we are not going to be able to write a `Â¢` function that inspects the second element of its lefthand operand to check if it's the `id` function; the identity of functions is not decidable. So the only way to satisfy Law 1 will be to have the first element of the result (`r`) be taken from the first element of the righthand operand in _all_ the cases when the first element of the lefthand operand is `r0`. But then that means that the result of the lhs of Law 5 will also have a first element of `r`; so, turning now to the rhs of Law 5, we see that `Â¢` must use the first element of its _left_hand operand (here again `r`) at least in those cases when the first element of its righthand operand is `r0`. If our `R` type has a natural *monoid* structure, we could just let `r0` be the monoid's identity, and have `Â¢` combine other `R`s using the monoid's operation. Alternatively, if the `R` type is one that we can safely apply the predicate `(r0==)` to, then we could define `Â¢` something like this: # safe_add (Some 12) (Some 4);;  : int option = Some 16 # safe_add (safe_div (Some 12) (Some 0)) (Some 4);;  : int option = None *) 
let (>>=) (u : 'a option) (j : 'a > 'b option) : 'b option =  match u with   None > None   Some x > j x;; + let (Â¢) (r1,f) (r2,x) = ((if r0==r1 then r2 else if r0==r2 then r1 else ...), ...) let map2 (f : 'a > 'b > 'c) (u : 'a option) (v : 'b option) : 'c option =  u >>= (fun x > v >>= (fun y > Some (f x y)));; +But for some types neither of these will be the case. For function types, as we already mentioned, `==` is not decidable. If the functions have suitable types, they do form a monoid with `â` as the operation and `id` as the identity; but many function types won't be such that arbitrary functions of that type are composable. So when `R` is the type of functions from `int`s to `bool`s, for example, we won't have any way to write a `Â¢` that satisfies the constraints stated above. let safe_add3 = map2 (+);; (* that was easy *) +For the third failure, that is examples of MapNables that aren't Monads, we'll just state that lists where the `map2` operation is taken to be zipping rather than taking the Cartesian product (what in Haskell are called `ZipList`s), these are claimed to exemplify that failure. But we aren't now in a position to demonstrate that to you. let safe_div3 (u: int option) (v: int option) =  u >>= (fun x > v >>= (fun y > if 0 = y then None else Some (x / y)));; Haskell has an even more userfriendly notation for defining `safe_div3`, namely: +## Further Reading ##  safe_div3 :: Maybe Int > Maybe Int > Maybe Int  safe_div3 u v = do {x < u;  y < v;  if 0 == y then Nothing else Just (x `div` y)} +As we mentioned above, the notions of Monads have their origin in Category Theory, where they are mostly specified in terms of (what we call) `â§` and `join`. For advanced study, here are some further links on the relation between monads as we're working with them and monads as they appear in Category Theory: +[1](http://en.wikipedia.org/wiki/Outline_of_category_theory) +[2](http://lambda1.jimpryor.net/advanced_topics/monads_in_category_theory/) +[3](http://en.wikibooks.org/wiki/Haskell/Category_theory) +[4](https://wiki.haskell.org/Category_theory) (where you should follow the further links discussing Functors, Natural Transformations, and Monads) +[5](http://www.stephendiehl.com/posts/monads.html) Let's see our new functions in action: 
(* # safe_div3 (safe_div3 (Some 12) (Some 2)) (Some 3);;  : int option = Some 2 # safe_div3 (safe_div3 (Some 12) (Some 0)) (Some 3);;  : int option = None # safe_add3 (safe_div3 (Some 12) (Some 0)) (Some 3);;  : int option = None *) +Here are some papers that introduced Monads into functional programming: + +* Eugenio Moggi, Notions of Computation and Monads: Information and Computation 93 (1) 1991. This paper is available online, but would be very difficult reading for members of this seminar, so we won't link to it. However, the next two papers should be accessible. + +* [Philip Wadler. The essence of functional programming](http://homepages.inf.ed.ac.uk/wadler/papers/essence/essence.ps): +invited talk, *19'th Symposium on Principles of Programming Languages*, ACM Press, Albuquerque, January 1992. + + +* [Philip Wadler. Monads for Functional Programming](http://homepages.inf.ed.ac.uk/wadler/papers/marktoberdorf/baastad.pdf): +in M. Broy, editor, *Marktoberdorf Summer School on Program Design +Calculi*, Springer Verlag, NATO ASI Series F: Computer and systems +sciences, Volume 118, August 1992. Also in J. Jeuring and E. Meijer, +editors, *Advanced Functional Programming*, Springer Verlag, +LNCS 925, 1995. Some errata fixed August 2001. + + +Here is some other reading: Compare the new definitions of `safe_add3` and `safe_div3` closely: the definition for `safe_add3` shows what it looks like to equip an ordinary operation to survive in dangerous presuppositionfilled world. Note that the new definition of `safe_add3` does not need to test whether its arguments are `None` values or real numbersthose details are hidden inside of the `bind` function.  Note also that our definition of `safe_div3` recovers some of the simplicity of the original `safe_div`, without the complexity introduced by `safe_div2`. We now add exactly what extra is needed to track the nodivisionbyzero presupposition. Here, too, we don't need to keep track of what other presuppositions may have already failed for whatever reason on our inputs.  (Linguistics note: Dividing by zero is supposed to feel like a kind of presupposition failure. If we wanted to adapt this approach to building a simple account of presupposition projection, we would have to do several things. First, we would have to make use of the polymorphism of the `option` type. In the arithmetic example, we only made use of `int option`s, but when we're composing natural language expression meanings, we'll need to use types like `N option`, `Det option`, `VP option`, and so on. But that works automatically, because we can use any type for the `'a` in `'a option`. Ultimately, we'd want to have a theory of accommodation, and a theory of the situations in which material within the sentence can satisfy presuppositions for other material that otherwise would trigger a presupposition violation; but, not surprisingly, these refinements will require some more sophisticated techniques than the supersimple Option/Maybe monad.) +* [Yet Another Haskell Tutorial on Monad Laws](http://en.wikibooks.org/wiki/Haskell/YAHT/Monads#Definition) +* [Haskell wikibook on Understanding Monads](http://en.wikibooks.org/wiki/Haskell/Understanding_monads) +* [Haskell wikibook on Advanced Monads](http://en.wikibooks.org/wiki/Haskell/Advanced_monads) +* [Haskell wiki on Monad Laws](http://www.haskell.org/haskellwiki/Monad_laws) +There's a long list of monad tutorials linked at the [[Haskell wikihttps://wiki.haskell.org/Monad_tutorials_timeline]] (we linked to this at the top of the page), and on our own [[Offsite Reading/readings]] page. (Skimming the titles is somewhat amusing.) If you are confused by monads, make use of these resources. Read around until you find a tutorial pitched at a level that's helpful for you.