projects
/
matthijs
/
master-project
/
report.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Remove todo.
[matthijs/master-project/report.git]
/
Chapters
/
Prototype.tex
diff --git
a/Chapters/Prototype.tex
b/Chapters/Prototype.tex
index 139b93e56be69f2637efcffc785935e95bb77b9c..b9e8aa73e2a88d5de0e5ebb139158842a8ce91d6 100644
(file)
--- 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.
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
\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}
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
\fxnote{This entire section on state annotations should be reviewed}
Ideal: Type synonyms, since there is no additional code overhead for