Add links to part 5 in compiler series

content/blog/00_compiler_intro.md

@@ -137,3 +137,4 @@ Here are the posts that I've written so far for this series:
 * [Parsing]({{< relref "02_compiler_parsing.md" >}})
 * [Typechecking]({{< relref "03_compiler_typechecking.md" >}})
 * [Small Improvements]({{< relref "04_compiler_improvements.md" >}})
+* [Execution]({{< relref "05_compiler_execution.md" >}})

content/blog/02_compiler_parsing.md

@@ -291,4 +291,4 @@ wrong:
 We are told an error occured. Excellent! We're not really sure what our tree looks like, though.
 We just know there's __stuff__ in the list of definitions. Having read our source code into
 a structure we're more equipped to handle, we can now try to verify that the code
-makes sense in [Part 3 - Type Checking]({{< relref "03_compiler_typechecking.md" >}})
+makes sense in [Part 3 - Type Checking]({{< relref "03_compiler_typechecking.md" >}}).

content/blog/03_compiler_typechecking.md

@@ -606,4 +606,4 @@ All of our examples print the number of declarations in the program,
 which means they don't throw 0. And so, we have typechecking!
 Before we look at how we will execute our source code,
 we will slow down and make quality of life improvements
-in our codebase in [Part 4 - Small Improvements]({{< relref "04_compiler_improvements.md" >}})
+in our codebase in [Part 4 - Small Improvements]({{< relref "04_compiler_improvements.md" >}}).

content/blog/04_compiler_improvements.md

@@ -234,3 +234,6 @@ cd build && make -j8
 We've made a lot of changes to the codebase, and I've only shown snippets of the code
 so far. If you'de like to see the whole codebase, you can go to my site's git repository
 and check out [the code so far](https://dev.danilafe.com/Web-Projects/blog-static/src/branch/master/code/compiler/04).
+
+Having taken this little break, it's time for our next push. We will define
+how our programs will be evaluated in [Part 5 - Execution]({{< relref "05_compiler_execution.md" >}}).