— Oh, right
We could say, for instance, that a variable assignment is the property of X scope, and do metaprogramming
— And cross-scope, know exactly where it came from
— You could manage source code from a top-down perspective during runtime, idk the formal term but it would be like "self-aware JS"
— Aaaah, like Lisp macros?
— A variable declaration is a directive to the parser to compute a scope and set a pointer to
undefined for that variable until the line gets executed
var thing = "hello", upon entry into a function call, runs code that allocates
undefined, then when it gets executed it simply swaps the pointer to the location in memory where the string is allocated
— They're tagged pointers carrying the name of the variable, too
— So yes... you would be able to look at this during run time if we are provided an abstraction to the
— You could look into the future, man
— And know, somewhere ahead of the current executing statement, there is a variable being declared but not allocated yet (due to not being executed yet)
— You could perhaps, at the top of your functions, get a list of all the variables being declared