Not sure how it's going to work but definitely want to add a step that allows someone to add a plug in into the compiler that can walk the ast and do whatever.
Use cases
Formatter:
add "Formatter On" and "Formatter Off" as annotations
walk the ast and write to the file the proper formatted output
Documentation:
add "Documentation" annotation
like java docs but with markdown support.
generate html/pdf/markdown docs by walking the ast and finding these documentation annotations.
the linked functions
Custom Analyzers
there is some configuration for finding the bad patterns in the ast
When walking the tree if it detects the bad pattern it can emit a compiler error/warning/info message (when i add more ide support these errors/warnings/infos can be picked up by the ide)
Questions
[ ] what language are the plug-ins implemented in?
[ ] how do we provide an api suitable for anything a user could want to do?
[ ] what limitations should we have?
[ ] when do the plug-ins run (before/after parsing or after semantic analysis or after code gen)? Should this be configurable?
Not sure how it's going to work but definitely want to add a step that allows someone to add a plug in into the compiler that can walk the ast and do whatever.
Use cases
Formatter:
Documentation:
Custom Analyzers
Questions