diff options
author | Chloe Brown <chloe.brown.00@outlook.com> | 2025-06-24 18:36:15 +0100 |
---|---|---|
committer | Chloe Brown <chloe.brown.00@outlook.com> | 2025-06-24 18:36:15 +0100 |
commit | e9c892020fbc92584321503ed5202d16de0b5923 (patch) | |
tree | fed58e86a5d8c08216e874f7331c812d8aa45410 /sec | |
parent | 0cbc4ea179c6c196b827dc59c8576108c86991ca (diff) |
Fix 230--234.
Diffstat (limited to 'sec')
-rw-r--r-- | sec/systemt.ltx | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/sec/systemt.ltx b/sec/systemt.ltx index cec4344..8b24706 100644 --- a/sec/systemt.ltx +++ b/sec/systemt.ltx @@ -288,10 +288,11 @@ constructors. For example, we can add the constructor \mathsf{double}(x) \coloneq \tuple{2 \cdot x.0, x.1} \] -Eliminator encodings inherit the weaknesses of Church encodings. Defining an -arbitrary fold requires polymorphism. Pattern matching is also impossible in the -general case. With our sum and depth example, we have no way of knowing whether -the value representing a tree came from a leaf or branch as we deliberately +Eliminator encodings inherit and extend the weaknesses of Church +encodings. Defining an arbitrary fold requires polymorphism in +general. Pattern matching is also impossible in the general case. With +our sum and depth example, we have no way of knowing whether the value +representing a tree came from a leaf or branch as we deliberately forget this information. \subsubsection*{Heap Encodings} |