> The ambitious and judicious folk can use parseStmt(whole file) for anything > already.
that has been discussed elsewhere already, it doesn't work in many cases since you get a different (duplicate) symbol, not the original symbol; this breaks down when symbols have state (eg a threadvar inside a proc) and many other corner cases once you start using it more, which I've tried before `moduleSymbols`. > The idea that we "can't go up the tree" is such a fundamental assumption in > the design of the language that I cannot fathom the extent of corruption > weakening this spec would foment. it's not going up the tree if you call `moduleSymbols(myModule)` from a module that imports `myModule`. And that's what --experimental flags are for. The feature has real use cases (repl, interactive docs, etc) and works for me just fine in my fork.
