From: jim Date: Mon, 9 Feb 2015 23:13:16 +0000 (-0500) Subject: tweak explanation of why `f` is curried X-Git-Url: http://lambda.jimpryor.net/git/gitweb.cgi?p=lambda.git;a=commitdiff_plain;h=bd49f089c4d7bc20ff9f722da579a2e54915d180 tweak explanation of why `f` is curried --- diff --git a/topics/week2_encodings.mdwn b/topics/week2_encodings.mdwn index 8b760e22..4f206852 100644 --- a/topics/week2_encodings.mdwn +++ b/topics/week2_encodings.mdwn @@ -274,7 +274,7 @@ Now, what should the `SOMETHING` be? Well, when we supply an `f` and a `z` we sh \f z. f a (f b (f c z)) -Here we work with curried functions, because as we explained at the end of the section on Tuples, that's the idiomatic and native style for passing multiple arguments in the Lambda Calculus. +Here we assume `f` to be a curried function, taking its arguments in the form `f c z` rather that `f (c, z)` (that is, `f (\h. h c z)`), because as we explained at the end of the section on Tuples, the curried form is the idiomatic and native style for passing multiple arguments in the Lambda Calculus. So if `[a, b, c]` should be the displayed higher-order function above, what should `[c]` be? Evidently: