Merge branch 'master' into working

[lambda.git] / exercises / assignment3.mdwn

diff --git a/exercises/assignment3.mdwn b/exercises/assignment3.mdwn
index 3615453..e2fd962 100644 (file)
--- a/exercises/assignment3.mdwn
+++ b/exercises/assignment3.mdwn
@@ -6,7 +6,7 @@
 
 2. What does `[ 10*x + y | y from [4], x from [1, 2, 3] ]` evalaute to?
 
 
 2. What does `[ 10*x + y | y from [4], x from [1, 2, 3] ]` evalaute to?
 

-3. Using either Kapulet's or Haskell's list comprehension syntax, write an expression that transforms `[3, 1, 0, 2]` into `[3, 3, 3, 1, 2, 2]`. [[Here is a hint|assignment3 hints]], if you need it.
+3. Using either Kapulet's or Haskell's list comprehension syntax, write an expression that transforms `[3, 1, 0, 2]` into `[3, 3, 3, 1, 2, 2]`. [[Here is a hint|assignment3 hint1]], if you need it.

 
 
 ## Lists
 
 
 ## Lists


@@ -17,14 +17,28 @@
 
 6. Continuing to encode lists in terms of their left-folds, what should `last` be, where `last [a, b, c]` should result in `c`. Let `last []` result in whatever `err` is bound to.
 
 
 6. Continuing to encode lists in terms of their left-folds, what should `last` be, where `last [a, b, c]` should result in `c`. Let `last []` result in whatever `err` is bound to.
 

-7. Continuing to encode lists in terms of their left-folds, how should we write `head`? This is challenging. [[Here is a hint|assignment3 hints]], if you need it.
+7. Continuing to encode lists in terms of their left-folds, how should we write `head`? This is challenging. [[Here is a solution|assignment3 hint2]], if you need help.

 
 
 ## Numbers
 
 8. Recall our proposed encoding for the numbers, called "Church's encoding". As we explained last week, it's similar to our proposed encoding of lists in terms of their folds. In last week's homework, you defined `succ` for numbers so encoded. Can you now define `pred` in the Lambca Calculus? Let `pred 0` result in whatever `err` is bound to. This is challenging. For some time theorists weren't sure it could be done. (Here is [some interesting commentary](http://okmij.org/ftp/Computation/lambda-calc.html#predecessor).) However, in this week's notes we examined one strategy for defining `tail` for our chosen encodings of lists, and given the similarities we explained between lists and numbers, perhaps that will give you some guidance in defining `pred` for numbers.
 
 
 
 ## Numbers
 
 8. Recall our proposed encoding for the numbers, called "Church's encoding". As we explained last week, it's similar to our proposed encoding of lists in terms of their folds. In last week's homework, you defined `succ` for numbers so encoded. Can you now define `pred` in the Lambca Calculus? Let `pred 0` result in whatever `err` is bound to. This is challenging. For some time theorists weren't sure it could be done. (Here is [some interesting commentary](http://okmij.org/ftp/Computation/lambda-calc.html#predecessor).) However, in this week's notes we examined one strategy for defining `tail` for our chosen encodings of lists, and given the similarities we explained between lists and numbers, perhaps that will give you some guidance in defining `pred` for numbers.
 

-9. Define `leq` for numbers (that is, ≤) in the Lambda Calculus.
+9. Define `leq` for numbers (that is, ≤) in the Lambda Calculus. Here is the expected behavior, 
+where `one` abbreviates `succ zero`, and `two` abbreviates `succ (succ zero)`.
+
+        leq zero zero ~~> true
+        leq zero one ~~> true
+        leq zero two ~~> true
+        leq one zero ~~> false
+        leq one one ~~> true
+        leq one two ~~> true
+        leq two zero ~~> false
+        leq two one ~~> false
+        leq two two ~~> true
+        ...
+
+    You'll need to make use of the predecessor function, but it's not essential to understanding this problem that you have successfully implemented it yet. You can treat it as a black box.

 
 ## Combinatorial Logic
 
 
 ## Combinatorial Logic
 


@@ -53,3 +67,21 @@ Using the mapping specified in this week's notes, translate the following lambda
 <!-- -->
 
 23. For each of the above translations, how many `I`s are there? Give a rule for describing what each `I` corresponds to in the original lambda term.
 <!-- -->
 
 23. For each of the above translations, how many `I`s are there? Give a rule for describing what each `I` corresponds to in the original lambda term.

+
+More Lambda Practice
+--------------------
+
+Reduce to beta-normal forms:
+
+<OL start=24>
+<LI>`(\x. x (\y. y x)) (v w)`
+<LI>`(\x. x (\x. y x)) (v w)`
+<LI>`(\x. x (\y. y x)) (v x)`
+<LI>`(\x. x (\y. y x)) (v y)`
+
+<LI>`(\x y. x y y) u v`
+<LI>`(\x y. y x) (u v) z w`
+<LI>`(\x y. x) (\u u)`
+<LI>`(\x y z. x z (y z)) (\u v. u)`
+</OL>
+