updates

[phd-thesis.git] / dsl / class_deep_embedding.tex

diff --git a/dsl/class_deep_embedding.tex b/dsl/class_deep_embedding.tex
index 1cd911f..e39a88e 100644 (file)
--- a/dsl/class_deep_embedding.tex
+++ b/dsl/class_deep_embedding.tex
@@ -263,7 +263,7 @@ e2p = Ext_2 (Lit_2 42 `Sub_2` Lit_2 1)
 \subsection{Unbraiding the semantics from the data}
 This approach does reveal a minor problem.
 Namely, that all semantics type classes are braided into our datatypes via the \haskelllhstexinline{Ext_2} constructor.
-Say if we add the printer again, the \haskelllhstexinline{Ext_2} constructor has to be modified to contain the printer type class constraint as well\footnote{Resulting in the following constructor: \haskelllhstexinline{forall x.(Eval_2 x, Print_2 x) => Ext_2 x}.}. %chktex 36
+Say if we add the printer again, the \haskelllhstexinline{Ext_2} constructor has to be modified to contain the printer type class constraint as well.\footnote{Resulting in the following constructor: \haskelllhstexinline{forall x.(Eval_2 x, Print_2 x) => Ext_2 x}.} %chktex 36
 Thus, if we add semantics, the main data type's type class constraints in the \haskelllhstexinline{Ext_2} constructor need to be updated.
 To avoid this, the type classes can be bundled in a type class alias or type class collection as follows.
 
@@ -805,7 +805,7 @@ instance (c (d c0), CreateRecord (d c0) cs) =>
 The class constraints for the interpretation instances can now be greatly simplified, as shown in the evaluation instance for \haskelllhstexinline{Expr}.
 The implementation remains the same, only that for the extension case, a trick needs to be applied to convince the compiler of the correct instances.
 Using \haskelllhstexinline{`In`}'s \haskelllhstexinline{project} function, a dictionary can be brought into scope.
-This dictionary can then subsequently be used to apply the type class function on the extension using the \haskelllhstexinline{withDict} function from the \haskelllhstexinline{Data.Constraint} library\footnote{\haskelllhstexinline{withDict :: Dict c -> (c => r) -> r}}.
+This dictionary can then subsequently be used to apply the type class function on the extension using the \haskelllhstexinline{withDict} function from the \haskelllhstexinline{Data.Constraint} library.\footnote{\haskelllhstexinline{withDict :: Dict c -> (c => r) -> r}}
 The \GHCmod{ScopedTypeVariables} extension is used to make sure the existentially quantified type variable for the extension is matched to the type of the dictionary.
 Furthermore, because the class constraint is not smaller than the instance head, \GHCmod{UndecidableInstances} should be enabled.