home! should reset orientation, not just location
@matt points out that home! described is just goto! (0, 0). So let's get rid of reset! and home! should operate as described in the issue title.
We got good enough error reporting for computer class! They're still not great; parsing errors are a mess of off-by-one. But definitely they did what the needed to.
Actually, the conversation leads us to think we should disallow shadowing.
One question is whether we allow shadowing of names bound in Prelude. The first thought is that yes, you can shadow…
One quick question here is whether we want a "turtle graphics protocol" or a more general I/O protocol, which starts with turtle graphics. To wit:
{ "turtle_graphics": [["forward",…There is almost certainly a way to use p5 transformations to make this work, but I reckon the thing to do here, now that computer class is all over, is to stand up a turtle graphics protocol out…
home! should reset orientation, not just location
Is this right? I think there's probably a reason to have home!, reset!, and clear! turtle commands:
home!brings the turtle back to the originreset!brings the turtle back to…
do forms
The issue is that the interpreter uses call-fn and should actually use apply-synth-term in passing the previous result to the next term in a do form. In other words, do should be sugar for…
Is the correct?
Technically, what happens when a function body is a block?
Well, a block is a new scope. So when the function body is a new block, it's a child scope, with the parent scope…