You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The cute trick here would be to capture the interpreter state just after evaluating each expression in Eval.evalBody (crucially, including the extended environment) and to return to Repl.process both the result of evaluating the current expression, and a suspended computation to run on the /next/ expression.
Yes, it's a bit unfortunate, I need to return to this problem when I get some time.
My thinking on the issue is that using ReaderT evaluator makes the tutorial a bit more understandable and accessible. For that, we lose a simple way to persist definitions: there's just no state to update!
For the evaluator, there must be a way to run eval, e -> a, capture that a, stick it in the e, then run the next line with the appended e.
The Repl doesn't remember definitions:
This works:
The text was updated successfully, but these errors were encountered: