From 49cf8e3e08958b5fdc075ba2ae8772393bcf7fea Mon Sep 17 00:00:00 2001 From: Danila Fedorin Date: Wed, 25 Mar 2020 17:40:40 -0700 Subject: [PATCH] Add links to the article everywhere else --- content/blog/00_compiler_intro.md | 1 + content/blog/09_compiler_garbage_collection.md | 4 ++-- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/content/blog/00_compiler_intro.md b/content/blog/00_compiler_intro.md index 924d2c0..84c6ae9 100644 --- a/content/blog/00_compiler_intro.md +++ b/content/blog/00_compiler_intro.md @@ -141,3 +141,4 @@ Here are the posts that I've written so far for this series: * [Runtime]({{< relref "07_compiler_runtime.md" >}}) * [LLVM]({{< relref "08_compiler_llvm.md" >}}) * [Garbage Collection]({{< relref "09_compiler_garbage_collection.md" >}}) +* [Polymorphism]({{< relref "10_compiler_polymorphism.md" >}}) diff --git a/content/blog/09_compiler_garbage_collection.md b/content/blog/09_compiler_garbage_collection.md index 72a6039..47366de 100644 --- a/content/blog/09_compiler_garbage_collection.md +++ b/content/blog/09_compiler_garbage_collection.md @@ -554,5 +554,5 @@ and can benefit from `let/in` expressions and __lambda functions__. Furthermore, our language is currently monomorphic, and would be much better with __polymorphism__. Finally, to make our language capable of more-than-trivial work, we may want to implement -__Input/Output__ and __strings__. I hope to see you in future posts, -where we will implement these features! +__Input/Output__ and __strings__. We tackle the largest of these +features, polymorphism, in [Part 10]({{< relref "10_compiler_polymorphism.md" >}}).