From f44e69a8fb636846ca36d0cfbe3247e30a3aa34e Mon Sep 17 00:00:00 2001 From: Matthijs Kooijman Date: Tue, 8 Dec 2009 18:18:07 +0100 Subject: [PATCH] Say something about using top level function instead of binder. --- Chapters/HardwareDescription.tex | 3 ++- Outline | 1 - 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Chapters/HardwareDescription.tex b/Chapters/HardwareDescription.tex index 3179cfe..f5e2615 100644 --- a/Chapters/HardwareDescription.tex +++ b/Chapters/HardwareDescription.tex @@ -152,7 +152,8 @@ and3 a b c = and (and a b) c In Haskell, there is no sharp distinction between a variable and a function: a function is just a variable (binder) with a function type. This means that a top level function is just any top level - binder with a function type. + binder with a function type. This also means that sometimes top level + function will be used when top level binder is really meant. As an example, consider the following Haskell snippet: diff --git a/Outline b/Outline index e24089c..4844ad2 100644 --- a/Outline +++ b/Outline @@ -58,4 +58,3 @@ TODO: Say something about the builtin functions somewhere (ref: christiaan) TODO: Future work: Use Cλash TODO: Abstract TODO: Preface -TODO: Top level function -> top level binder -- 2.30.2