Personal tools

User:Michiexile/MATH198/Lecture 9

From HaskellWiki

< User:Michiexile | MATH198(Difference between revisions)
Jump to: navigation, search
Line 4: Line 4:
 
===Recursion patterns===
 
===Recursion patterns===
   
((X, Y and Z)) identified in the paper ((Bananas et.c.)) a number of generic patterns for recursive programming that they had observed, catalogued and systematized. The aim of that paper is to establish a number of ''rules'' for modifying and rewriting expressions involving these generic recursion patterns.
+
Meijer, Fokkinga & Patterson identified in the paper ''Functional programming with bananas, lenses, envelopes and barbed wire'' a number of generic patterns for recursive programming that they had observed, catalogued and systematized. The aim of that paper is to establish a number of ''rules'' for modifying and rewriting expressions involving these generic recursion patterns.
   
 
As it turns out, these patterns are instances of the same phenomenon we saw last lecture: where the recursion comes from specifying a different algebra, and then take a uniquely existing morphism induced by initiality (or, as we shall see, finality).
 
As it turns out, these patterns are instances of the same phenomenon we saw last lecture: where the recursion comes from specifying a different algebra, and then take a uniquely existing morphism induced by initiality (or, as we shall see, finality).
Line 25: Line 25:
   
 
Onwards to recursion schemes!
 
Onwards to recursion schemes!
  +
  +
We shall define a few specific morphisms we'll use repeatedly. This notation, introduced here, occurs all over the place in these corners of the literature, and are good to be aware of in general:
  +
* If <math>a: TA\to A</math> is an initial algebra for <math>T</math>, we denote <math>a = in_A</math>.
  +
* If <math>a: A\to TA</math> is a final coalgebra for <math>T</math>, we denote <math>a = out_A</math>.
  +
* We write <math>\mu f</math> for the fixed point operator
  +
<haskell>
  +
mu f = x where x = f x
  +
</haskell>
  +
* MFP write <math>(f\Delta g)</math> for
  +
<haskell>
  +
Delta f g = \x -> (f x, g x)
  +
</haskell>
  +
* MFP write <math>(f\nabla g) x</math> for
  +
<haskell>
  +
(Nabla f g) (Left x) = f x
  +
(Nabla f g) (Right x) = g x
  +
</haskell>
  +
  +
These two last constructions are directly motivated by the maps induced from the universal properties of products and coproducts.
  +
  +
We shall write <math>(f\times g)</math> and <math>(f+g)</math> for the <math>\Delta</math> and <math>\nabla</math> constructions, respectively.
  +
  +
We note that in the situation considered by MFP, inital algebras and final coalgebras coincide, and thus <math>in_A, out_A</math> are the pair of isomorphic maps induced by either the initial algebra- or the final coalgebra-structure.
   
 
====Catamorphisms====
 
====Catamorphisms====
Line 40: Line 63:
 
m (a, n) = n+1
 
m (a, n) = n+1
 
</haskell>
 
</haskell>
  +
  +
MFP define the catamorphism by, supposing <hask>T</hask> is initial for the functor <hask>F</hask>:
  +
<haskell>
  +
cata :: (F a b -> b) -> T a -> b
  +
cata phi = mu (\x -> phi . fmap x . outT)
  +
</haskell>
  +
  +
We can reframe the example above as a catamorphism by observing that here,
  +
<haskell>
  +
data F a b = Nil | Cons a b deriving (Eq, Show)
  +
type T a = [a]
  +
  +
instance Functor (F a) where
  +
fmap _ Nil = Nil
  +
fmap f (Cons n a) = Cons n (f a)
  +
  +
outT :: T a -> F a (T a)
  +
outT [] = Nil
  +
outT (a:as) = Cons a as
  +
  +
lphi :: F a Int -> Int
  +
lphi Nil = 0
  +
lphi (Cons a n) = n + 1
  +
  +
l = cata lphi
  +
</haskell>
  +
where we observe that <hask>mu</hask> has a global definition for everything we do and <hask>out</hask> is defined once we settle on the functor <hask>F</hask> and its initial algebra. Thus, the definition of <hask>phi</hask> really is the only place that the recursion data shows up.
   
 
====Anamorphisms====
 
====Anamorphisms====
Line 66: Line 116:
 
</haskell>
 
</haskell>
 
which is exactly the recursion we wrote to begin with.
 
which is exactly the recursion we wrote to begin with.
  +
  +
MFP define the anamorphism by a fixpoint as well, namely:
  +
<haskell>
  +
ana psi = mu (\x -> inT . fmap x . psi)
  +
</haskell>
  +
  +
We can, again, recast our illustration above into a structural anamorphism, by:
  +
<haskell>
  +
-- Reuse mu, F, T from above
  +
inT :: F a (T a) -> T a
  +
inT Nil = []
  +
inT (Cons a as) = a:as
  +
  +
fpsi :: Int -> F Int Int
  +
fpsi 0 = Nil
  +
fpsi n = Cons n (n-1)
  +
</haskell>
  +
  +
  +
  +
   
 
====Hylomorphisms====
 
====Hylomorphisms====

Revision as of 22:49, 16 November 2009

IMPORTANT NOTE: THESE NOTES ARE STILL UNDER DEVELOPMENT. PLEASE WAIT UNTIL AFTER THE LECTURE WITH HANDING ANYTHING IN, OR TREATING THE NOTES AS READY TO READ.


Contents

1 Recursion patterns

Meijer, Fokkinga & Patterson identified in the paper Functional programming with bananas, lenses, envelopes and barbed wire a number of generic patterns for recursive programming that they had observed, catalogued and systematized. The aim of that paper is to establish a number of rules for modifying and rewriting expressions involving these generic recursion patterns.

As it turns out, these patterns are instances of the same phenomenon we saw last lecture: where the recursion comes from specifying a different algebra, and then take a uniquely existing morphism induced by initiality (or, as we shall see, finality).

Before we go through the recursion patterns, we need to establish a few pieces of theoretical language, dualizing the Eilenberg-Moore algebra constructions from the last lecture.

1.1 Coalgebras for endofunctors

Definition If P: C\to C is an endofunctor, then a P-coalgebra on A is a morphism a: A\to PA.

A morphism of coalgebras: f: a\to b is some f: A\to B such that the diagram

CoalgebraMorphism.png

commutes.

Just as with algebras, we get a category of coalgebras. And the interesting objects here are the final coalgebras. Just as with algebras, we have

Lemma (Lambek) If a: A\to PA is a final coalgebra, it is an isomorphism.

Finally, one thing that makes us care highly about these entities: in an appropriate category (such as ω − CPO), initial algebras and final coalgebras coincide, with the correspondence given by inverting the algebra/coalgebra morphism. In Haskell not quite true (specifically, the final coalgebra for the lists functor gives us streams...).

Onwards to recursion schemes!

We shall define a few specific morphisms we'll use repeatedly. This notation, introduced here, occurs all over the place in these corners of the literature, and are good to be aware of in general:

  • If a: TA\to A is an initial algebra for T, we denote a = inA.
  • If a: A\to TA is a final coalgebra for T, we denote a = outA.
  • We write μf for the fixed point operator
mu f = x where x = f x
  • MFP write (fΔg) for
Delta f g = \x -> (f x, g x)
  • MFP write (f\nabla g) x for
(Nabla f g) (Left x) = f x
(Nabla f g) (Right x) = g x

These two last constructions are directly motivated by the maps induced from the universal properties of products and coproducts.

We shall write (f\times g) and (f + g) for the Δ and \nabla constructions, respectively.

We note that in the situation considered by MFP, inital algebras and final coalgebras coincide, and thus inA,outA are the pair of isomorphic maps induced by either the initial algebra- or the final coalgebra-structure.

1.2 Catamorphisms

A catamorphism is the uniquely existing morphism from an initial algebra to a different algebra. We have to define maps down to the return value type for each of the constructors of the complex data type we're recursing over, and the catamorphism will deconstruct the structure (trees, lists, ...) and do a generalized fold over the structure at hand before returning the final value.

The intuition is that for catamorphisms we start essentially structured, and dismantle the structure.

Example: the length function from last lecture. This is the catamorphism for the functor P_A(X) = 1 + A\times X given by the maps

u :: Int
u = 0
 
m :: (A, Int) -> Int
m (a, n) = n+1
MFP define the catamorphism by, supposing
T
is initial for the functor
F
:
cata :: (F a b -> b) -> T a -> b
cata phi = mu (\x -> phi . fmap x . outT)

We can reframe the example above as a catamorphism by observing that here,

data F a b = Nil | Cons a b deriving (Eq, Show)
type T a = [a]
 
instance Functor (F a) where
  fmap _ Nil = Nil
  fmap f (Cons n a) = Cons n (f a)
 
outT :: T a -> F a (T a)
outT [] = Nil
outT (a:as) = Cons a as
 
lphi :: F a Int -> Int
lphi Nil = 0
lphi (Cons a n) = n + 1
 
l = cata lphi
where we observe that
mu
has a global definition for everything we do and
out
is defined once we settle on the functor
F
and its initial algebra. Thus, the definition of
phi
really is the only place that the recursion data shows up.

1.3 Anamorphisms

An anamorphism is the categorical dual to the catamorphism. It is the canonical morphism from a coalgebra to the final coalgebra for that endofunctor.

Here, we start unstructured, and erect a structure, induced by the coalgebra structures involved.

Example: we can write a recursive function

first :: Int -> [Int]
first 1 = [1]
first n = n : first (n - 1)

This is an anamorphism from the coalgebra for P_{\mathbb N}(X) = 1 + \mathbb N\times X on \mathbb N generated by the two maps

c 0 = Left ()
c n = Right (n, n-1)

and we observe that we can chase through the diagram

CoalgebraMorphism.png

to conclude that therefore

f 0 = []
f n = n : f (n - 1)

which is exactly the recursion we wrote to begin with.

MFP define the anamorphism by a fixpoint as well, namely:

ana psi = mu (\x -> inT . fmap x . psi)

We can, again, recast our illustration above into a structural anamorphism, by:

-- Reuse mu, F, T from above
inT :: F a (T a) -> T a
inT Nil = []
inT (Cons a as) = a:as
 
fpsi :: Int -> F Int Int
fpsi 0 = Nil
fpsi n = Cons n (n-1)



1.4 Hylomorphisms

1.5 Metamorphisms

1.6 Paramorphisms

1.7 Apomorphisms

2 Further reading

Terminology in the literature: in and out, inl, inr.


3 Homework

  1. Write a fold for the data type
    data T a = L a | B a a | C a a a
    and demonstrate how this can be written as a catamorphism by giving the algebra it maps to.
  2. The integers have a partial order induced by the divisibility relation. We can thus take any integer and arrange all its divisors in a tree by having an edge n \to d if d | n and d doesn't divide any other divisor of n. Write an anamorphic function that will generate this tree for a given starting integer. Demonstrate how this function is an anamorphism by giving the algebra it maps from.