This commit is contained in:
Rowan Torbitzky-Lane 2025-01-31 03:10:39 -06:00
parent fa2b16443f
commit 8be1431458
2 changed files with 2 additions and 1 deletions

View File

@ -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. * [x] tests/ are just copied from make-grade, need to write for this project.
* [ ] Included examples of basic assertions, QuickCheck, Hspec, hspec-quickcheck. * [ ] Included examples of basic assertions, QuickCheck, Hspec, hspec-quickcheck.
* [x] Look at Lenses library for abstraction * [x] Look at Lenses library for abstraction
* [ ] Use Plushy genomes for this project.
## Design considerations ## Design considerations
The biggest design constraint is that for the exec stack (but not data stacks) The biggest design constraint is that for the exec stack (but not data stacks)

View File

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