Bananas, Lenses, Envelopes and Barbed Wire
A Translation Guide

by Edward Z. Yang

One of the papers I've been slowly rereading since summer began is "Functional Programming with Bananas, Lenses, Envelopes and Barbed Wire", by Erik Meijer, Maarten Fokkinga and Ross Paterson. If you want to know what {cata,ana,hylo,para}morphisms are, this is the paper to read: section 2 gives a highly readable formulation of these morphisms for the beloved linked list.

Last time, however, my eyes got a little bit glassy when they started discussing algebraic data types, despite having used and defined them in Haskell; part of me felt inundated in a sea of triangles, circles and squiggles, and by the time they reached the laws for the basic combinators, I might as well have said, "It's all math to me!"

A closer reading revealed that, actually, all of these algebraic operators can be written out in plain Haskell, and for someone who has been working with Haskell for a little bit of time, this can provide a smoother (albeit more verbose) reading. Thus, I present this translation guide.

Type operators. By convention, types are A, B, C\ldots on the left and a, b, c... on the right. We distinguish these from function operators, though the paper does not and relies on convention to distinguish between the two.

A \dagger B \Leftrightarrow Bifunctor t => t a b
A_F \Leftrightarrow Functor f => f a
A* \Leftrightarrow [a]
D \parallel D' \Leftrightarrow (d, d')
D\ |\ D' \Leftrightarrow Either d d'
_I \Leftrightarrow Identity
\underline{D} \Leftrightarrow Const d
A_{(FG)} \Leftrightarrow (Functor f, Functor g) => g (f a)
A_{(F\dagger G)} \Leftrightarrow (Bifunctor t, Functor f, Functor g) => Lift t f g a
\boldsymbol{1} \Leftrightarrow ()

(For the pedantic, you need to add Hask Hask Hask to the end of all the Bifunctors.)

Function operators. By convention, functions are f, g, h\ldots on the left and f :: a -> b, g :: a' -> b', h... on the right (with types unified as appropriate).

f \dagger g \Leftrightarrow bimap f g :: Bifunctor t => t a a' -> t b b'
f_F \Leftrightarrow fmap f :: Functor f => f a -> f b
f \parallel g \Leftrightarrow f *** g :: (a, a') -> (b, b')
    where f *** g = \(x, x') -> (f x, g x')
\grave{\pi} \Leftrightarrow fst :: (a, b) -> a
\acute{\pi} \Leftrightarrow snd :: (a, b) -> b
f \vartriangle g \Leftrightarrow f &&& g :: a -> (b, b')        -- a = a'
    where f &&& g = \x -> (f x, g x)
\Delta x \Leftrightarrow double :: a -> (a, a)
    where double x = (x, x)
f\ |\ g \Leftrightarrow asum f g :: Either a a' -> Either b b'
    where asum f g (Left x)  = Left (f x)
          asum f g (Right y) = Right (g y)
\grave{\i} \Leftrightarrow Left :: a -> Either a b
\acute{\i} \Leftrightarrow Right :: b -> Either a b
f\ \triangledown\ g \Leftrightarrow either f g :: Either a a' -> b        -- b = b'
\nabla x \Leftrightarrow extract x :: a
    where extract (Left x) = x
          extract (Right x) = x
f \rightarrow g \Leftrightarrow (f --> g) h = g . h . f
    (-->) :: (a' -> a) -> (b -> b') -> (a -> b) -> a' -> b'
g \leftarrow f \Leftrightarrow (g <-- f) h = g . h . f
    (<--) :: (b -> b') -> (a' -> a) -> (a -> b) -> a' -> b'
(f \overset{F}{\leftarrow} g) \Leftrightarrow (g <-*- f) h = g . fmap h . f
    (<-*-) :: Functor f => (f b -> b') -> (a' -> f a) -> (a -> b) -> a' -> b'
f_I \Leftrightarrow id f :: a -> b
f\underline{D} \Leftrightarrow const id f :: a -> a
x_{(FG)} \Leftrightarrow (fmap . fmap) x
VOID \Leftrightarrow const ()
\mu f \Leftrightarrow fix f

Now, let's look at the abides law:

(f \vartriangle g)\ \triangledown\ (h \vartriangle j) = (f\ \triangledown\ h) \vartriangle (g\ \triangledown\ j)

Translated into Haskell, this states:

either (f &&& g) (h &&& j) = (either f h) &&& (either g j)

Which (to me at least) makes more sense: if I want to extract a value from Either, and then run two functions on it and return the tuple of results, I can also split the value into a tuple immediately, and extract from the either "twice" with different functions. (Try running the function manually on a Left x and Right y.)