Message from JavaScript talks

May 2017

— Kek, labels in the github repo, but never used

— 

You really need a stack AND some sort of way to label each node as discovered or undiscovered for any sort of tree search?

— I kept them for style

— Well, the map does this functionally

— Marking objects is not an option

— Would create an impure function with any number of side effects

— I did explore marking fully, though, it just isn't feasable

— The efficiency tanks drastically when you then need to unmark objects

— The reason you need to do it at all is to detect and mitigate cycles/infinite loops, but it also means multiple properties pointing to the same object will be correctly represented

Message permanent page

— The stack just represents a list of tuples yet to be traversed, not nodes seen before

— Sorry oot,anyone have telegram sysadmin grup?

— linux_group is probably the closest