Web-Projects/blog-static
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Add links to the article everywhere else
All checks were successful
continuous-integration/drone/push Build is passing
Details

Browse Source
This commit is contained in:
Danila Fedorin 2020-03-25 17:40:40 -07:00
parent c53a8ba68e
commit 49cf8e3e08
2 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
content/blog/00_compiler_intro.md
View File

@ -141,3 +141,4 @@ Here are the posts that I've written so far for this series:
* [Runtime]({{< relref "07_compiler_runtime.md" >}}) * [Runtime]({{< relref "07_compiler_runtime.md" >}})
* [LLVM]({{< relref "08_compiler_llvm.md" >}}) * [LLVM]({{< relref "08_compiler_llvm.md" >}})
* [Garbage Collection]({{< relref "09_compiler_garbage_collection.md" >}}) * [Garbage Collection]({{< relref "09_compiler_garbage_collection.md" >}})
* [Polymorphism]({{< relref "10_compiler_polymorphism.md" >}})

4
content/blog/09_compiler_garbage_collection.md
View File

@ -554,5 +554,5 @@ and can benefit from `let/in` expressions and __lambda functions__.
Furthermore, our language is currently monomorphic, and would Furthermore, our language is currently monomorphic, and would
be much better with __polymorphism__. Finally, to make our language be much better with __polymorphism__. Finally, to make our language
capable of more-than-trivial work, we may want to implement capable of more-than-trivial work, we may want to implement
__Input/Output__ and __strings__. I hope to see you in future posts, __Input/Output__ and __strings__. We tackle the largest of these
where we will implement these features! features, polymorphism, in [Part 10]({{< relref "10_compiler_polymorphism.md" >}}).