shares

[msc-thesis1617.git] / conclusion.tex

diff --git a/conclusion.tex b/conclusion.tex
index bde2501..729f479 100644 (file)
--- a/conclusion.tex
+++ b/conclusion.tex
@@ -25,7 +25,7 @@ broken device without needing to recompile the code.
 
 \section{Discussion}
 \todo{class based shallow doesn't have multiple backend support}
-\todo{slow client software because of intepretation}
+\todo{slow client software because of interpretation}
 \todo{What happens if a device dies? Task resending, add to handshake}
 
 
@@ -56,7 +56,10 @@ of the client software. However, it could be implemented as a compile-time
 option and exchanged during the handshake so that the server knows the
 multithreading capabilities of the client.
 
-\todo{Parametric lenses on devices share?}
+Hardly any work has been done in the interpreter. The current interpreter is a
+no nonsense stack machine. A lot of improvements can be done in this part. For
+example, precomputed \emph{gotos} can improve jumping to the correct part of
+the code corresponding to the correct instruction.
 
 \subsection{Resources}
 Resource analysis during compilation can be useful to determine if an
@@ -67,7 +70,7 @@ given.
 
 This idea could be extended to the analysis of stack size and possibly
 communication bandwidth. With this functionality ever more reliable fail-over
-systems can be designed. When the system knows more precise bounds it can
+systems can be designed. When the system knows preciser bounds it can
 allocate more \glspl{Task} on a device whilst staying within safe memory
 bounds. The resource allocation can be done at runtime within the backend
 itself or a general backend can be devices that can calculate the resources