comments

README.md

@@ -22,6 +22,7 @@ worth it in the grand scheme. Would mean we could also track the functions when
     * [x] tests/ are just copied from make-grade, need to write for this project.
     * [ ] Included examples of basic assertions, QuickCheck, Hspec, hspec-quickcheck.
 * [x] Look at Lenses library for abstraction
+* [ ] Use Plushy genomes for this project.
 
 ## Design considerations
 The biggest design constraint is that for the exec stack (but not data stacks)

src/Push.hs

@@ -64,7 +64,7 @@ interpretExec state@(State {_exec = e : es}) =
     (StateFunc func) -> interpretExec $ func state {_exec = es}
     (Block block) -> interpretExec (state {_exec = block ++ es})
     (PlaceInput val) -> interpretExec (state {_exec = (view input state Map.! val) : es})
-    Close -> undefined -- remove Close constructor later?
+    Close -> undefined
 interpretExec state = state
 
 -- Need to make interpretExec strict, right?