From 8be14314588cfa6f0ca15ac181573a364c8d9282 Mon Sep 17 00:00:00 2001
From: Rowan Torbitzky-Lane <rowan.a.tl@protonmail.com>
Date: Fri, 31 Jan 2025 03:10:39 -0600
Subject: [PATCH] comments

---
 README.md   | 1 +
 src/Push.hs | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 78db742..7192751 100644
--- a/README.md
+++ b/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)
diff --git a/src/Push.hs b/src/Push.hs
index 2d3ebd2..0367d59 100644
--- a/src/Push.hs
+++ b/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?