From 1746011c1642395ece4b3858e9ff52b7e76f2c18 Mon Sep 17 00:00:00 2001 From: Danila Fedorin Date: Sun, 21 Jun 2020 00:51:04 -0700 Subject: [PATCH] Publish 12th part of compiler series. --- content/blog/12_compiler_let_in_lambda/index.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/content/blog/12_compiler_let_in_lambda/index.md b/content/blog/12_compiler_let_in_lambda/index.md index 8b0f3db..82da98b 100644 --- a/content/blog/12_compiler_let_in_lambda/index.md +++ b/content/blog/12_compiler_let_in_lambda/index.md @@ -1,9 +1,8 @@ --- title: Compiling a Functional Language Using C++, Part 12 - Let/In and Lambdas -date: 2020-04-20T20:15:16-07:00 +date: 2020-06-21T00:50:07-07:00 tags: ["C and C++", "Functional Languages", "Compilers"] description: "In this post, we extend our language with let/in expressions and lambda functions." -draft: true --- Now that our language's type system is more fleshed out and pleasant to use, it's time to shift our focus to the ergonomics of the language itself. I've been mentioning `let/in` and __lambda__ expressions for a while now. The former will let us create names for expressions that are limited to a certain scope (without having to create global variable bindings), while the latter will allow us to create functions without giving them any name at all.