reason, \small{GHC} runs its simplifications and optimizations on the core
representation as well \cite[jones96].
- However, we will use the normal core representation, not the simplified
- core. Reasons for this are detailed below. \todo{Ref}
+ We will use the normal Core representation, not the simplified Core. Even
+ though the simplified Core version is an equivalent, but simpler
+ definition, some problems were encountered with it in practice. The
+ simplifier restructures some (stateful) functions in a way the normalizer
+ and the \VHDL generation cannot handle, leading to uncompilable programs
+ (whereas the non-simplified version more closely resembles the original
+ program, allowing the original to be written in a way that can be
+ handled). This problem is further discussed in
+ \in{section}[sec:normalization:stateproblems].
The final prototype roughly consists of three steps:
% Implementation issues: state splitting, linking input to output state,
% checking usage constraints on state variables.
%
-% \todo{Implementation issues: Separate compilation, simplified core.}
%
% vim: set sw=2 sts=2 expandtab:
\mainlanguage [en]
\setuppapersize[A4][A4]
\setuppagenumbering[alternative=doublesided]
-% Enable interaction (clickable links), but don't use special link colors.
-\setupinteraction[state=start,color=,contrastcolor=]
+% Enable interaction (clickable links), but don't use special link colors or a
+% bold style.
+\setupinteraction[state=start,color=,contrastcolor=,style=normal]
% Enable interaction in the table of contents as well
\setupcombinedlist[content][interaction=all]