A lot of people who like functional programming often give the reason that the functional style is simply more elegant than the imperative style. When compelled or inspired to explain (as I did in my old post, How I Learned to Love Functional Programming), they often point to the three “higher-order” functions map, fold, and filter, as providing a unifying framework for writing and reasoning about programs. But how unifying are they, really? In this post we’ll give characterizations of these functions in terms of universal properties, and we’ll see that in fact fold is the “most” universal of the three, and its natural generalization gives a characterization of transformations of standard compound data types.

By being *universal* or having a *universal property, *we don’t mean that map, fold, and filter are somehow mystically connected to all programming paradigms. That might be true, but it’s not the point of this article. Rather, by saying something has a universal property we are making a precise mathematical statement that it is either an initial or final object (or the unique morphism determined by such) in some category.

That means that, as a fair warning to the reader, this post assumes some basic knowledge of category theory, but no more than what we’ve covered on this blog in the past. Of particular importance for the first half of this post is the concept of a universal property, and in the followup post we’ll need some basic knowledge of functors.

## Map, Filter, and Fold

Recalling their basic definitions, *map* is a function which accepts as input a list whose elements all have the same type (call it ), and a function which maps to another type . Map then applies to every entry of to produce a new list whose entries all have type .

In most languages, implementing the map function is an elementary exercise. Here is one possible definition in ML.

fun map(_, nil) = nil | map(f, (head::tail)) = f(head) :: map(f, tail)

Next, *filter* takes as input a boolean-valued predicate on types and a list whose entries have type , and produces a list of those entries of which satisfy the predicate. Again, it’s implementation in ML might be:

fun filter(_, nil) = nil | filter(p, (head::tail)) = if p(head) then (head :: filter(p, tail)) else filter(p, tail)

Finally, *fold* is a function which “reduces” a list of entries with type down to a single value of type . It accepts as input a function , and an initial value , and produces a value of type by recursively applying as follows:

fun fold(_, v, nil) = v | fold(f, v, (head::tail)) = f(head, fold(f, v, tail))

(If this definition is mysterious, you’re probably not ready for the rest of this post.)

One thing that’s nice about fold is that we can define map and filter in terms of it:

fun map(f, L) = fold((fn x, xs => (f(x):xs)), [], L) fun filter(p, L) = fold((fn x, xs => if p(x) then x:xs else xs end), [], L)

We’ll see that this is no accident: fold happens to have the “most general” universality of the three functions, but as a warm-up and a reminder we first investigate the universality of map and filter.

## Free Monoids and Map

Map is the easiest function of the three to analyze, but to understand it we need to understand something about monoids. A monoid is simple to describe, it’s just a set with an associative binary operation denoted by multiplication and an identity element for that operation.

A *monoid homomoprhism* between two monoids is a function such that . Here the multiplication on the left hand side of the equality is the operation from and on the right it’s the one from (this is the same definition as a group homomorphism). As is to be expected, monoids with monoid homomorphisms form a category.

We encounter simple monoids every day in programming which elucidate this definition. Strings with the operation of string concatenation form a monoid, and the empty string acts as an identity because concatenating a string to the empty string has no effect. Similarly, lists with list concatenation form a monoid, where the identity is the empty list. A nice example of a monoid homomorphism is the length function. We know it’s a homomorphism because the length of a concatenation of two lists is just the sum of the lengths of the two lists.

Integers also form a monoid, with addition as the operation and zero as the identity element. However, the list and string monoids have an extra special property that integers do not. For a number you can always find so that is the identity element. But for lists, the only way to concatenate two lists and get the empty list is if both of the lists were empty to begin with. A monoid with this property is called *free, *and to fully understand it we should make a definition which won’t seem to mean anything at first.

**Definition: **Let be a category. Given a set , the *free object* over , denoted , is an object of which is universal with respect to set-maps for any object in .

As usual with a definition by universal property, we should elaborate as to exactly what’s going on. Let be a category whose objects are sets and let a set, possibly not in this category. We can construct a new category, whose objects are set-maps

and whose morphisms are commutative diagrams of the form

where is a morphism in . In other words, we simply require that for every .

By saying that the *free monoid* on satisfies this universal property for the category of monoids, we really mean that it is *initial* in this category of set-maps and commutative diagrams. That is, there is a monoid and a set-map so that for every monoid and set-map there is a *unique* monoid homomorphism from to . In other words, there is a unique monoid homomorphism making the following diagram commute:

For example, if is the set of all unicode characters, then is precisely the monoid of all strings on those characters. The map is then the map taking a character to the single-character string ““. More generally, if is any type in the category of types and computable functions, then is the type of homogeneous lists whose elements have type .

We will now restrict our attention to lists and types, and we will denote the free (list) monoid on a type as . The universal property of map is then easy to describe, it’s just a specific instance of this more general universal property for the free monoids. Specifically, we work in the sub-category of homogeneous list monoids (we only allow objects which are for some type ). The morphism just takes a value of type and spits out a single-item list . **We might hope** that for any mapping , there is a unique monoid homomorphism making the following diagram commute.

And while this is true, the diagram lies because “map” does not achieve what does. The map might send all of to the empty list, and this would cause to be the trivial map. But if we decomposed further to require it to send to a single , such as

then things work out nicely. In particular, specifying a function uniquely defines how a list homomorphism operates on lists. In particular, the diagram forces the behavior for single-element lists: . And the property of being a monoid homomorphism forces to preserve order.

Indeed, we’ve learned from this analysis that the *structure* of the list involved is crucial in forming the universal property. Map is far from the only computable function making the diagram commute, but it is clearly the only monoid homomorphism. As we’ll see, specifying the order of operations is more generally described by fold, and we’ll be able to restate the universal property of map without relying on monoid homomorphisms.

## Filter

The filter function is a small step up in complexity from map, but its universal property is almost exactly the same. Again filter can be viewed through the lens of a universal property for list monoids, because filter itself takes a predicate and produces a list monoid. We know this because filtering two lists by the same predicate and concatenating them is the same as concatenating them first and then filtering them. Indeed, the only difference here is that the diagram now looks like this

where is our predicate, and is defined by and . The composition gives the map that we can extend uniquely to a monoid homomorphism . We won’t say any more on it, except to mention that again maintaining the order of the list is better described via fold.

## Fold, and its Universal Property

Fold is different from map and filter in a very concrete way. Even though map and filter do specify that the order of the list should be preserved, it’s not an important part of their definition: filter should filter, and map should map, but no interaction occurs between different entries during the computation. In a sense, we got lucky that having everything be monoid homomorphisms resulted in preserving order without our specific intention.

Because it doesn’t necessarily produce lists and the operation can be quite weird, fold cannot exist without an explicit description of the order of operations. Let’s recall the definition of fold, and stick to the “right associative” order of operations sometimes specified by calling the function “foldr.” We will use foldr and fold interchangeably.

fun foldr(_, v, nil) = v | foldr(f, v, (head::tail)) = f(head, foldr(f, v, tail))

Even more, we can’t talk about foldr in terms of monoids. Even after fixing and , foldr need not produce a monoid homomorphism. So if we’re going to find a universal property of foldr, we’ll need a more general categorical picture.

One first try would be to view foldr as a morphism of sets

The mapping is just , and this is just the code definition we gave above. One might hope that this mapping defines an isomorphism in the category of types and programs, but it’s easy to see that it does not. For example, let

Then the left hand side of the mapping above is a set of size 8 (there are eight ways to combine a choice of element in with a map from ). But the right hand size is clearly infinite. In fact, it’s *uncountably *infinite, though not all possible mappings are realizable in programs of a reasonable length (in fact, very few are). So the morphism can’t possibly be a surjective and hence is not an isomorphism.

So what *can *we say about fold? The answer is a bit abstract, but it works out nicely.

Say we fix a type for our lists, . We can define a category which has as objects the following morphisms

By we mean the type with one value (null, if you wish), and is a morphism from a coproduct (i.e. there are implicit parentheses around ). As we saw in our post on universal properties, a morphism from a coproduct is the same thing as a pair of functions which operates on each piece. Here one operates on and the other on . Since morphisms from are specified by the image of the sole value , we will often write such a function as , where .

Now the morphisms in are the pairs of morphisms which make the following diagram commute:

Here we write because it is determined by in a canonical way. It maps in the only way one can, and it maps . So we’re really specifying alone, but as we’ll see it’s necessary to include as well; it will provide the “inductive step” in the definition of fold.

Now it turns out that fold satisfies the universal property of being *initial* in this category. Well, not quite. We’re saying first that the following object is initial,

Where cons is the list constructor which sends . By being initial, we mean that for any object given by the morphism , there is a unique morphism from . The “fold” is precisely this unique morphism, which we denote by . We implicitly know its “barred” counterpart making the following diagram commute.

This diagram has a lot going on in it, so let’s go ahead and recap. The left column represents an object we’re claiming is initial in this crazy category we’ve made. The right hand side is an arbitrary object , which is equivalently the data of an element and a mapping . This is precisely the data needed to define fold. The dashed lines represent the unique morphisms making the diagram commute, whose existence and uniqueness is the defining property of what it means for an object to be initial in this category. Finally, we’re claiming that foldr, when we fix and , makes this diagram commute, and is hence the very same unique morphism we seek.

To prove all of this, we need to first show that the object is initial. That is, that any two morphisms we pick from must be equal. The first thing to notice is that the two objects and are really the same thing. That is, has a two-sided inverse which makes it an isomorphism in the category of types. Specifically, the inverse is the map sending

So if we have a morphism from , and the diagram commutes, we can see that . We’re just going the long way around the diagram.

Supposing that we have two such morphisms , we can prove they are equal by induction on the length of the input list. It is trivial to see that they both must send the empty list to . Now suppose that for lists of length the two are equal. Given a list we see that

where the last equality holds by the commutativity of the diagram. Continuing,

where the last equality holds by the inductive hypothesis. From here, we can reverse the equalities using and it’s “barred” version to get back to , proving the equality.

To show that fold actually makes the diagram commute is even simpler. In order to make the diagram commute we need to send the empty list to , and we need to inductively send to , but this is the very definition of foldr!

So we’ve established that fold has this universal property. It’s easy now to see how map and filter fit into the picture. For mapping types to via , just use the type in place of above, and have , and have be the empty list. Filter similarly just needs a special definition for .

A skeptical reader might ask: what does all of this give us? It’s a good question, and one that shouldn’t be taken lightly because I don’t have an immediate answer. I do believe that with some extra work we could use universal properties to give a trivial proof of the third homomorphism theorem for lists, which says that any function expressible as both a foldr and a foldl can be expressed as a list homomorphism. The proof would involve formulating a universal property for foldl, which is very similar to the one for foldr, and attaching the diagrams in a clever way to give the universal property of a monoid homomorphism for lists. Caveat emptor: this author has not written such a proof, but it seems likely that it would work.

More generally, any time we can represent the requirements of a list computation by an object like , we can represent the computation as a foldr. What good does this do us? Well, it might already be obvious when you can and can’t use fold. But in addition to *proving* when it’s possible to use fold, this new perspective generalizes very nicely to give us a characterization of *arbitrary* computations on compound data types. One might want to know when to perform fold-like operations on trees, or other sufficiently complicated beasts, and the universal property gives us a way to see when such a computation is possible.

That’s right, I said it: there’s more to the world than lists. Shun me if you must, but I will continue dream of great things.

In an effort to make the egregiously long posts on this blog slightly shorter, we’ll postpone our generalization of the universal property of fold until next time. There we’ll define “initial algebras” and show how to characterize “fold-like” computations any compound data type.

Until then!

Thanks for the post! Could you sketch how you might formulate a universal property for foldl?

LikeLike

I believe it would just be to change the square diagram for fold by switching the order of [A] x A. Does that make sense?

LikeLike

If you rearrange the argument order and fix only f, fold does produce a monoid homomorphism, in particular a monoid action.

fold :: (a -> Endo b) -> [a] -> Endo b

This is just a special-case of the free monoid adjunction which gives rise to a fold with type:

fold :: Monoid m => (a -> m) -> [a] -> m

Naturality (parametricity) in a gives fold/map fusion.

LikeLike

There is a universal property for foldl, but in Haskell it isn’t symmetric with the one for foldr, because of strictness issues (see Exercise 16 in http://dx.doi.org/10.1007/978-3-540-44833-4_1).

I would love to see a “trivial proof” of the Third Homomorphism Theorem! Do try. Note that foldr is nicely datatype-generic (there’s a fold for every algebraic datatype), but foldl is not obviously so (what is the analogue to foldl on binary trees?) Therefore, the 3HT as I wrote about it is just for lists, not datatype-generic. Morihata et al (http://dx.doi.org/10.1145/1480881.1480905) give a datatype-generic construction of the 3HT, but it builds on top of zippers; I don’t see how that will lead to a “trivial proof”. And the proofs I have aren’t in the form of categorical diagram-chasing – a crucial lemma is that, for every computable total function h with enumerable domain, there is a computable (partial) function g such that h . g . h = h.

LikeLike

It’s been a while since I wrote this, and I haven’t though about it at all since, but I do still want to try. Usually in algebra these sorts of things fall out from observations about the uniqueness of the decomposition, but I may have jumped the gun in calling it trivial :) You’re certainly more familiar with the material than I am.

LikeLike

“There we’ll define “initial algebras” and show how to characterize “fold-like” computations any compound data type.”, are you referring to monads in the above statement?

LikeLike

No, not specifically.

LikeLike

When do you plan to write that next article. These series are very helpful.

So what are “fold-like” computations on other compound data types?

LikeLike

If you can imagine folding over a list then you can imagine folding over a tree. Well compound data structures are just trees, and there is a generalization of the whole framework here to that setting. Look up initial algebras and catamorphisms. (I think, it’s been a while since I thought about this stuff…)

LikeLike