@ngn Interesting, but the parens are necessary and breaks the rule that parenthesising something doesn't change it's meaning. Also, arguments are un-APLy, even if practical. You'd be able to do I←[]? Also [] is very confusable with ⌷ since context doesn't help.
@ngn for trains, at least, there's no way to make them work without some overhead. But there definitely are ways to not require a primitive function to be 4 chars long
@dzaima yea im still figuring it out. usually you can just act like everything is immutable and pattern match which makes it nice for writing networked-services. this level of manipulation seems to be mostly reserved for BEAM vm hackers.
i miight have a path fwd using make_ref/0 and storing a datastructure of key-value pairs where the key is a unique reference and the value is the variable
Would just like to report that the new TryAPL.org needs some more testing. Half the time when I am using it, it just completely breaks. Shift key no longer works, Alt + up/down and history no longer works. It seems very fragile
it seems like this isn't unheard of to reimplement a heap & gc in erlang for a vm https://github.com/rvirding/luerl/blob/develop/src/luerl_heap.erl#L517
might just write initial version w/o gc and manually kill/restart the entire process
i am avoiding having to dip into a NIF or port (either an in-process C API or a separate process that communicates over a socket)
@cannadayr Looks like it would be pretty easy to copy that garbage collector too. The BQN version should be smaller since scopes/environments are the only kind of dynamically allocated mutable data, and it looks like the Lua VM has four different things to track.
And the possible types of reference are array elements, block variables, block parents, and compound functions. So the mark() functions should be simpler as well, but you do have to make sure to expose the components of compound functions (trains and derived funtions) somehow if you don't want them to leak.
found a video on youtube about luerl and skimmed thru it "the main difficulty of luerl implementation was the need to implement Lua's mutable global data with erlang's immutable local data" 🤔
so, if I have an array of variable references: [Ref1,Ref2,undefined]
and a list of {reference,value} tuples [{Ref1,[1,2,3]},{Ref2,[3,4,5]}] i can change a variable by updating the reference [Ref1,Ref2,undefined] becomes [Ref1,Ref1,undefined] the value the reference is pointing to doesnt change, I just mutate to a new reference
@dzaima Probably because that makes the JS code think Alt is being held, since it never registers Alt being let go, and then Up/Down are treated like Alt+Up/Down.
