Book Image

Haskell Design Patterns

By : Tikhon Jelvis, Ryan Lemmer
Book Image

Haskell Design Patterns

By: Tikhon Jelvis, Ryan Lemmer

Overview of this book

Design patterns and idioms can widen our perspective by showing us where to look, what to look at, and ultimately how to see what we are looking at. At their best, patterns are a shorthand method of communicating better ways to code (writing less, more maintainable, and more efficient code) This book starts with Haskell 98 and through the lens of patterns and idioms investigates the key advances and programming styles that together make "modern Haskell". Your journey begins with the three pillars of Haskell. Then you'll experience the problem with Lazy I/O, together with a solution. You'll also trace the hierarchy formed by Functor, Applicative, Arrow, and Monad. Next you'll explore how Fold and Map are generalized by Foldable and Traversable, which in turn is unified in a broader context by functional Lenses. You'll delve more deeply into the Type system, which will prepare you for an overview of Generic programming. In conclusion you go to the edge of Haskell by investigating the Kind system and how this relates to Dependently-typed programming
Table of Contents (14 chapters)

Arrows


Let's find our way towards arrows from the perspective of monads. Consider the following IO code:

import System.IO
main = do 
main = liftM (length . words)
                   (readFile "jabberwocky.txt" )
            >>= print
-- regular functions: length, words
-- Monadic functions: readFile, print

We use liftM to lift the composed function length . words into the monadic function readFile and then feed the result to another monadic function, print.

We can compose the regular functions with (.), but we know well that we cannot do the following:

  print . length . words . readFile "jabberwocky.txt"
  -- INVALID - types don't align

Let's make the preceding code possible!

Note

The following code is based on a combination of Programming with Arrows by John Hughes, and a blog post by John Wiegley at http://www.newartisans.com/2012/10/arrows-are-simpler-than-they-appear/.

The crux of our approach will be to create a "meta type" to represent monadic IO functions and then define composition...