Sign In Start Free Trial

Haskell Design Patterns

By : Lemmer

4.1 (9)

Haskell Design Patterns

4.1 (9)

By: 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

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

1. Functional Patterns – the Building Blocks

1. Functional Patterns – the Building Blocks

Higher-order functions

Currying functions

Recursion

Types, pattern matching, and polymorphism

Lazy evaluation

Monads

Summary

2. Patterns for I/O

2. Patterns for I/O

I/O as a first class citizen

Imperative I/O

Lazy I/O

The problems with lazy I/O

Resource management with bracket

Iteratee I/O

Summary

3. Patterns of Composition

3. Patterns of Composition

Functor

Applicative functor

Monad

Monad transformers

Arrows

Summary

4. Patterns of Folding and Traversing

4. Patterns of Folding and Traversing

Folding over lists

Summary

5. Patterns of Type Abstraction

5. Patterns of Type Abstraction

Abstracting function types: RankNTypes

Abstracting datatypes

Abstracting type-classes

Summary

6. Patterns of Generic Programming

6. Patterns of Generic Programming

Patterns of generic programming

The sum of products style

Origami programming

Scrap your boilerplate

Summary

7. Patterns of Kind Abstraction

7. Patterns of Kind Abstraction

Higher-order kinds

Higher-kinded polymorphism

Associated type synonyms

Type (synonym) families

Kind polymorphism

Type promotion

Type-level programming

Dependently-typed programming

Summary

Epilogue

Index

Index

Customer Reviews

4.1 (9)

5 star

55.6%

4 star

22.2%

3 star

11.1%

2 star

0

1 star

11.1%

Higher-order functions

Functions are our first kind of "glue" in Haskell.

Functions as first-class citizens

Haskell functions are first-class citizens of the language. This means that:

We can name a function just as we can name any primitive value:
```
square = \x -> x * x
```
We can pass functions to other functions:
```
map square [1, 3, 5, 7]
```
(Here, map is a higher-order function.)
Functions can produce other functions (here, by currying the foldr function):
```
sum = foldr (+) 0
```

Functions can form part of other data structures:

let fs = [(* 2), (* 3), (* 5)]
zipWith (\f v -> f v) fs [1, 3, 5]

This places Haskell functions on an equal footing with primitive types.

Composing functions

Let's compose these three functions, f, g, and h, in a few different ways:

f, g, h :: String -> String

The most rudimentary way of combining them is through nesting:

z x = f (g (h x))

Function composition gives us a more idiomatic way of combining functions:

z' x = (f . g . h) x

Finally, we can abandon any reference to arguments:

z'' = f . g . h

This leaves us with an expression consisting of only functions. This is the "point-free" form.

Programming with functions in this style, free of arguments, is called tacit programming.

It is hard to argue against the elegance of this style, but in practice, point-free style can be more fun to write than to read: it can become difficult to infer types (and, therefore, meaning). Use this style when ease of reading is not overly compromised.

Search

Your notes and bookmarks