We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Something I've experimented with a little bit is a reflection API provided by the parser.
You provide it a generated AST (or multiple ASTs) and the struct is able to traverse the AST to search for function declarations, classes, etc.
You would then be able to call methods on the struct to find a particular class, function, get type information, params etc.
This would do a lot of heavy lifting for static analysis tools, dead code finders, interpreters etc.
The text was updated successfully, but these errors were encountered:
reflection can be a whole different project in it's own repository.
it is possible to build a reflection system from AST, see https://github.com/Roave/BetterReflection for reference.
Sorry, something went wrong.
yeah, whether its part of this repo or not, doesn't bother me. just noting down ideas surrounding the parser
Not related to parser, closing.
No branches or pull requests
Something I've experimented with a little bit is a reflection API provided by the parser.
You provide it a generated AST (or multiple ASTs) and the struct is able to traverse the AST to search for function declarations, classes, etc.
You would then be able to call methods on the struct to find a particular class, function, get type information, params etc.
This would do a lot of heavy lifting for static analysis tools, dead code finders, interpreters etc.
The text was updated successfully, but these errors were encountered: