From 9bb3281de202ae2e33675885eaca9936c76a8a82 Mon Sep 17 00:00:00 2001 From: Matthijs Kooijman Date: Wed, 9 Sep 2009 17:53:31 +0200 Subject: [PATCH] Add a bit content to a new Future Work chapter. --- Chapters/Future.tex | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 Chapters/Future.tex diff --git a/Chapters/Future.tex b/Chapters/Future.tex new file mode 100644 index 0000000..10a883a --- /dev/null +++ b/Chapters/Future.tex @@ -0,0 +1,22 @@ +\chapter{Future work} +\section{Improved notation for hierarchical state} +The hierarchic state model requires quite some boilerplate code for unpacking +and distributing the input state and collecting and repacking the output +state. There is really only one way in which this state handling can be done, +so it would make sense to hide this boilerplate. This would incur no +flexibility cost at all, since there are no other ways that would work. + +Options: Misuse the do notation in Haskell, create some abstraction in +Haskell or add new syntax. + +\section{Improved notation or abstraction for pipelining} +Since pipelining is a very common optimization for hardware systems, it should +be easy to specify a pipelined system. Since it involves quite some registers +into an otherwise regular combinatoric system, we might look for some way to +abstract away some of the boilerplate for pipelining. + +Example of naive pipelined code + +Using monadic do does not fit the typing + +Using custom combinators would work -- 2.30.2