From: Matthijs Kooijman <matthijs@stdin.nl>
Date: Fri, 4 Dec 2009 09:48:10 +0000 (+0100)
Subject: Make a small start on the state annotations section.
X-Git-Tag: final-thesis~108
X-Git-Url: https://git.stderr.nl/gitweb?a=commitdiff_plain;h=3a0ce128bb7bc501eeef368d2406d26b9652a8f3;p=matthijs%2Fmaster-project%2Freport.git

Make a small start on the state annotations section.
---

diff --git a/Chapters/HardwareDescription.tex b/Chapters/HardwareDescription.tex
index f5c0eaa..24afd89 100644
--- a/Chapters/HardwareDescription.tex
+++ b/Chapters/HardwareDescription.tex
@@ -885,7 +885,7 @@ acc in s = (s', out)
 
         \todo{Sidenote: One or more state arguments?}
 
-    \subsection{Explicit state annotation}
+    \subsection[sec:description:stateann]{Explicit state annotation}
       To make our stateful descriptions unambigious and easier to translate,
       we need some way for the developer to describe which arguments and
       results are intended to become stateful.
diff --git a/Chapters/Prototype.tex b/Chapters/Prototype.tex
index 139b93e..67d23c8 100644
--- a/Chapters/Prototype.tex
+++ b/Chapters/Prototype.tex
@@ -681,6 +681,10 @@
       here)}.
         
   \section[sec:prototype:statetype]{State annotations in Haskell}
+    As noted in \in{section}[sec:description:stateann], Cλash needs some
+    way to let the programmer explicitly specify which of a function's
+    arguments and which part of a function's result represent the
+    function's state.
       \fxnote{This entire section on state annotations should be reviewed}
 
       Ideal: Type synonyms, since there is no additional code overhead for