Message from JavaScript discussions

May 2017

— It's memory efficient, right?


Heres the tuple mechanism, runs after the strategy so it can have a chance to edit the tuple beforehand

— Yes, thats one benefit

— Although with recursive metacomposition your state information explodes

— So thankfully it offsets that

— Is metacomposition only possible with labels?

— That was the gimmick, right?

— No, you can do it with a stack too

— I settled on that

— The stack is the standin for the real call stack

— I see

— It just happens to be iddfs, just the best way to implement traversal with metacomposition