Block a user
Should Ludus distinguish between functions and procedures?
JS worker thread code should have an event loop
functions defined in functions should properly close over upvalues the second time they are run
I think this may be behind #87. It certainly doesn't help.
functions defined in functions should properly close over upvalues the second time they are run
Most minimal example:
fn foo (n) -> {
fn bar () -> n
}
foo (:foo) ()
foo (:bar) ()
functions defined in functions should properly close over upvalues the second time they are run
New datum:
map (even?, [1, 2, 3])
print! ("c") & console=> "false"
More minimal example:
map (inc, [1, 2, 3])
map (dec, [1,2 , 3]) &=> [2, 3, 4]
What's happening is…
My public transit textile sketch should work
Done: it was broken by a change in representing turtle state. Added a function, savestate that gets the current turtle_0 state. Meanwhile, turtle ::state () will return the state of the…
My public transit textile sketch should work
clear should clear the screen of turtle paths
The command stack should be optimized
In place of paths being more efficient, we've decided that it's easier/better to make commands more efficient: squash the commands when we ask for them, instead of doing it when we calculate the…
Keyboard interaction should work
Also, definitely related to #50: this will work much better once we're not drawing a bunch of teeny tiny sub-pixel lines to make paths.