Exercise 1.41 of SICP asks us to work out what the following expression will evaluate to, given the definition of
If this expression had side-effects, we’d need to understand the evaluation order and keep track of state changes with each evaluation step. Because this is a pure function, we can substitute the definitions of each sub-expression, and in any order we like. I found these substitutions quite tricky though, because with each evaluation of
double I had to take into account its argument. I ended up with something like this:
I found this quite hard to follow. I had to use additional intermediary steps (not shown above) to evaluate expressions like
(double (lambda (x) (inc (inc x)))).
Using other equalities
Instead of direct substitution we can transform the expression into equivalent terms we find easier to reason about, such as those with mathematical properties we can apply to simplify the expression. We still use substitution, but with other equalities instead of replacing a term’s name with its definition.
For this example, I found it easier to think of
double in terms of function composition.
Function composition is associative (which we can convince ourselves of using equalities1). I find this made it easier to reduce the nested
Composition lets us deal with functions as values without having to substitute in for their arguments at each step. The fact composition is associative hides unimportant details, such as not having to worry about the order of composition in expressions like
(double . double) . (double . double). I found each step made more sense to me, and I had more confidence in my answer.
I imagine different people will find different forms easier than others, but the point is we can choose whichever transformations we like to get the expression into an equivalent form we can work with more easily.
For a while now I’ve appreciated that pure functions mean we can more easily use substitution to understand code, but it wasn’t until this exercise that I’ve finally started to get a vague idea of what equational reasoning means. It is more than just substitution – it is being able to use all sorts of transformations and properties to understand our code. I don’t think this example really showcases this idea, but I did feel like it was my first glimpse into a different, powerful way of understanding code.