 # Defining infinite structures in Haskell

This article is part of a series on Haskell about how easy it is to define infinite structures in really concise ways. Building on the previous article about lazy evaluation, we explore how to define infinite structures using recursion without using a base case. While in other languages this would result in an infinite loop, this does not happen in Haskell due to its powerful lazy evaluation strategy.

## First steps: an infinite list of ones

Recall from the previous post that in Haskell, parameters are evaluated only when they are needed. Let us revisit a simple example. Consider the following function definition.

Calling f with parameters a = 2 + 3 and b = 3 * 3 would result in the following execution:

Notice how the value of the parameter b is never computed. More importantly, if the parameter b did not contain a simple arithmetic expression, but rather some thing more complex, Haskell would not waste time computing its value. Moreover, if the parameter b was undefined, i.e. if it could not be computed, the function call f a b would not fail.

Now consider the following definition:

What do you think would happen if we called ones? Well, ones is defined recursively, but it does not have a base case, so normally we would say that execution does not terminate, or that a maximum depth of recursion is reached and the program stops, or something along those lines. In Haskell, this is still true, calling ones directly will result in the program never stopping.

But, what if we called take 3 ones. Remember that the function take n xs returns the first n elements of the list xs. And indeed,

This not only doesn’t fail, but returns the expected result. Let’s look at the definition of take.

And let’s look at how Haskell handles the call take 3 ones.

Magic! As the expression take 3 ones did not depend on the full, infinite, list of ones, only the relevant part was evaluated and Haskell was able to correctly compute the expected result!

## More interesting infinite definitions

Base-case-less recursions need not be that simple. Assume we want to represent all of the natural numbers in Haskell. We could easily do so with

And indeed,

(Exercise: try to expand the call stack for take 2 nats as we did before)

This is a common enough case that Haskell has special syntax1 for it:

## The sieve of Erathostenes

Erathosthenes was a Greek mathematician who gave an algorithm to find all prime numbers up to a limit. The algorithm is similar to trial division, only it is constructive (i.e. instead of testing wether a number is prime, it finds all prime numbers up to a limit). Lets look at the pseudocode

1. List all numbers starting with 2 until n, where n is the upper bound in our search for primes.
2. Take the first element p in the list and remove all multiples of $p$ from the list, i.e. remove 2p, 3p, 4p, ... from the list. Another way to think of this is, remove a number x if mod x p == 0.
3. Go back to the previous step starting with the first remaining number.

This algorithm may be used without an upper bound if one wishes to find all of the prime numbers. In most languages this would not be possible but it is in Haskell:

And indeed,

Lazy evaluation is a powerful evaluation strategy that allows us to concisely and expressively write definitions of infinite structures. In future posts, we will explore other consequences of this design decision of the Haskell language and some situations in which it does not prove so useful.

1. You might have seen the syntax [a..b] before. It is a shorthand for the function enumFromTo defined in the enum class. In fact, [a..] is also a shorthand for the method enumFrom. Integers in Haskell are an instance of the Enum class that defines these methods.