When the term *Y Combinator* is mentioned in most technology circles today, the image it usually conjures up is of the well known startup incubator with their orange logo and a list of famous funded companies. There’s a very interesting reason they chose this name, and their FAQ page ^{1} gives some context on why they did so,

The Y combinator is one of the coolest ideas in computer science. It’s also a metaphor for what we do. It’s a program that runs programs; we’re a company that helps start companies.

Which of course begs the question – why are Y Combinators so cool and are there any real reasons to know about them?

This post aims to provide insight into some practical applications of Y Combinators, and I highly recommend reading some of the following resources on the topic that do a great job in articulating the theory behind them. ^{2} ^{3} ^{4}

## A gentle introduction

Let’s assume we want to write a recursive function that does something useful, but with a catch – we don’t want to invoke this recursive function * directly* from within itself. Why would we want to do this? Multiple reasons might force us to – perhaps we’d like to avoid stack overflows, or perhaps there are other deeper reasons which are out of the scope of this post.

^{5}

^{6}. Irrespective – how then would we go about doing so?

In other words, the problem we’re trying to solve is to “introduce a self reference to the function, without a **direct **self reference”.

Before diving into the programming aspects, let’s consider this in a purely mathematical form. A recursive function can be defined partly by itself. So, in the case of the Fibonacci series,

Now, how would we give such a recursive function an input, such that its output is the same as its input? For example, in the following function,

there are two inputs: 0 and 1, for which the function’s output is the same as the input provided to it. This is defined as the **fixed-point **of this function.

If we can now find a fixed-point *p *of *F* such that *F(p)* is equivalent to *p*, we can use *F(p) *or *p *interchangeably* (*since they are the same thing*) *as the “recursive” function without direct self-reference ^{7}.

It turns out that for any generic λ-expression *f* , is a fixed-point of *f *^{8}.

Given this, we can build a function that returns a fixed-point for any function *f *by taking the function in as an argument:

This is known as the fixed point or Y combinator. Therefore, for any function *f*, *Y(f) *is a fixed-point of *f. *That is, *f(Y(f)) *is equivalent to *Y(f).*

## A real world example

So far so good. But how is this useful and why should you know about it? Let’s examine the case of a Clojure function that gives us the sum of a sequence of numbers ^{9}.

1 2 3 4 5 6 7 8 |
;; An example of a recursive function to sum a sequence of numbers (defn sum-seq [x] (if (empty? x) 0 (+ (first x) (sum-seq (rest x))))) ;; invokes itself ;; (sum-seq [1 9]) ;; => 10 |

As we can see, this function invokes itself at the very last line, which is the kind of behavior we’re trying to avoid. How would we write this without a direct self reference? One way to think about this is to express it as a sequence of function calls that starts by being given a function, and returns to us not the result itself, but a sequence of “next” functions to compute the sum of that sequence. Here’s an example,

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 |
;; Function that returns the next function to compute the sum of a sequence of numbers (defn sum-seq-fn-gen [func] (fn [s] (if (empty? s) 0 (+ (first s) (func (rest s)))))) ;; user> ((sum-seq-fn-gen nil) []) ;; 0 ;; user> ((sum-seq-fn-gen (sum-seq-fn-generator nil)) [9]) ;; 9 ;; user> ((sum-seq-fn-gen (sum-seq-fn-gen (sum-seq-fn-gen nil))) [1 9]) ;; 10 |

This looks like it works. But as we can see, in order to get the sum for a two element vector, we needed to invoke this function thrice – clearly not a great use of our editing skills or time. How would we make this simpler? By simply finding the fixed point for this function, we could achieve what we set out to do! ^{10}. Let’s start by writing a fixed point combinator.

1 2 3 4 5 6 7 |
;; Y combinator (defn Y [m] ;; λf ((fn [future] ;; λx (future future)) ;; f(x x) (fn [future] ;; λx (m (fn [arg] ((future future) arg)))))) ;; f(x x) |

If we were to pass the sum-seq-gen function to this Y combinator we just wrote above, life becomes much simpler.

1 2 3 4 5 |
;; user> ((Y sum-seq-fn-gen) [1 2 3]) ;; 6 ;; user> ((Y sum-seq-fn-gen) (range 0 1000)) ;; 499500 |

So far so good. But the real power of a combinator isn’t just that it allows us to just write non-direct-reference recursive functions. It is that it allows us to create very useful wrappers around our functions, which can allow us to achieve all sorts of cool things without ever needing to rewrite our original function. As an example, let’s consider the use case of needing to log every internal function call that’s going on in the sum-seq-fn function. In the regular programming model, we would need to add these log lines to the sum-seq-fn itself, which is a huge overhead. But by using combinators, we can just define a LoggingY that will do this for us.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 |
;; A logging fixed point combinator (defn LoggingY [r] ((fn [f] (do (prn "Logging call: " f) (f f))) (fn [f] (do (prn "Logging within second f: " f) (r (fn [x] (do (prn "logging within third fn: " x) ((f f) x)))))))) viksit.explorations> ((LoggingY sum-seq-fn-gen) [1 2 3]) "Logging call: " #<explorations$LoggingY$fn__14921 viksit.explorations$LoggingY$fn__14921@1ed99bdc> "Logging within second f: " #<explorations$LoggingY$fn__14921 viksit.explorations$LoggingY$fn__14921@1ed99bdc> "logging within third fn: " (2 3) "Logging within second f: " #<explorations$LoggingY$fn__14921 viksit.explorations$LoggingY$fn__14921@1ed99bdc> "logging within third fn: " (3) "Logging within second f: " #<explorations$LoggingY$fn__14921 viksit.explorations$LoggingY$fn__14921@1ed99bdc> "logging within third fn: " () 6 |

Without having to change the original function, we’ve just added some deep instrumentation into our function.

## A memoization example

Let’s consider a slightly more non trivial example. What if we wanted to make a recursive function more efficient by introducing memoization? Could we write a generic non-recursive function and then apply an equally generic combinator to memoize it? Absolutely!

For this exercise, let’s define a more generic fixed point U combinator ^{11}, which applies an “abstract” function myapply on to the function f. We can use the freedom of choosing myapply, for example, to *transparently* interpose memoization.

1 2 3 4 |
;; U = λh.(h h) ;; Generic U combinator (defn U [f] (f f)) |

1 2 3 4 5 6 |
;; More generic function that can take an application function (defn UM [myapply f] (defn g [v] (fn [args] (myapply (f v) args))) (f g)) |

1 2 3 4 5 6 |
;; A non recursive function that gives us the nth fibonacci number (defn fib-nr [f] (fn [n] (if (< n 2) 1 (+ ((f f) (- n 1)) ((f f) (- n 2)))))) |

We can now create a combinator ready ^{12} function that returns an anonymous function that will cache a function’s arguments and results for it.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
(defn make-memoizer [] (let [application-cache (atom {})] (fn [function & args] (if-let [e (find @application-cache args)] (val e) (let [result (apply function args)] (swap! application-cache assoc args result) result))))) ;; Time taken to fetch the 38th fibonacci number viksit.explorations> (time ((U fib-nr) 38)) "Elapsed time: 9700.194 msecs" 63245986 ;; Time taken to fetch the same, but with memoization (!) viksit.explorations> (time ((UM (make-memoizer) fib-nr) 38)) "Elapsed time: 0.153 msecs" 63245986 |

As we can see, by never having to modify the original function, we’ve been able to use a variety of specific or generic combinators to provide wrappers that can help in making programs more optimal, easier to debug and ultimately, fine-tune.

- http://www.ycombinator.com/faq/ ↩
- https://medium.com/@ayanonagon/the-y-combinator-no-not-that-one-7268d8d9c46 ↩
- http://matt.might.net/articles/implementation-of-recursive-fixed-point-y-combinator-in-javascript-for-memoization ↩
- https://mitpress.mit.edu/sicp/full-text/book/book-Z-H-26.html#%_sec_4.1 ↩
- http://en.wikipedia.org/wiki/Stack_overflow ↩
- http://aegis.sourceforge.net/auug97.pdf ↩
- Seriously, highly recommend reading up on what fixed point combinators really mean ↩
- http://en.wikipedia.org/wiki/Lambda_calculus ↩
- Courtesy http://www.fatvat.co.uk/2009/04/understanding-y-combinator.html ↩
- This almost seemed like magic the first time I encountered it! ↩
- http://lambda-the-ultimate.org/classic/message5463.html ↩
- http://stackoverflow.com/questions/15859673/fixed-point-combinators ↩