X-Git-Url: https://git.stderr.nl/gitweb?p=matthijs%2Fmaster-project%2Freport.git;a=blobdiff_plain;f=Chapters%2FPrototype.tex;h=b9e8aa73e2a88d5de0e5ebb139158842a8ce91d6;hp=139b93e56be69f2637efcffc785935e95bb77b9c;hb=b21616e3601566e7b89293af948de0e0505dfc48;hpb=feee31da167a3c0505d2683d3e81e2597743f1a6

diff --git a/Chapters/Prototype.tex b/Chapters/Prototype.tex
index 139b93e..b9e8aa7 100644
--- a/Chapters/Prototype.tex
+++ b/Chapters/Prototype.tex
@@ -51,8 +51,6 @@
     primary compiler, \GHC, provides a high level API to its internals, made
     Haskell an obvious choice.
 
-    \note{There should be evaluation of the choice of Haskell and \VHDL}
-
   \section[sec:prototype:output]{Output format}
     The second important question is: What will be our output format? Since
     our prototype won't be able to program FPGA's directly, we'll have to have
@@ -681,6 +679,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