X-Git-Url: https://git.stderr.nl/gitweb?p=matthijs%2Fmaster-project%2Freport.git;a=blobdiff_plain;f=Chapters%2FNormalization.tex;h=907411e877ef6bb9d2d1a30c67fd5d94774527a5;hp=bf0d3884bd2047d69e87d29d52fa826fefcf31ed;hb=492b0d8d81c104b4b85fd1963a9d4a8b53f00e92;hpb=91b4bb893a7915a0701fcaafcd160cdf0460a1b6

diff --git a/Chapters/Normalization.tex b/Chapters/Normalization.tex
index bf0d388..907411e 100644
--- a/Chapters/Normalization.tex
+++ b/Chapters/Normalization.tex
@@ -2079,8 +2079,6 @@
         matching, causing a state input to be unpacked multiple times or
         be unpacked and repacked only in some of the code paths.
 
-        \todo{example?}
-
         Without going into detail about the exact problems (of which
         there are probably more than have shown up so far), it seems
         unlikely that these problems can be solved entirely by just
@@ -2090,6 +2088,9 @@
         of course mean that the intended normal form definition must be
         extended as well to be more specific about how state handling
         should look like in normal form.
+        \in{Section}[sec:prototype:statelimits] already contains a
+        tight description of the limitations on the use of state
+        variables, which could be adapted into the intended normal form.
 
   \section[sec:normalization:properties]{Provable properties}
     When looking at the system of transformations outlined above, there are a