Replies: 1 comment
-
This is now completed. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In the beginning, I went ahead and build ABI/ContractInfo parsers by utilizing antlr-go parser directly. Idea was to have these parsers available at will.
This approach is good if you need only ABI or ContractInfo from any specific contract, however, it's a very bad design if you need AST, Contract and ABI including any future solutions such as IR or SMT.
Right now each listener will re-parse the entire tree for all of the packages stated above. Therefore, I suggest to use AST parser to parse the source code once and modify abi and contracts packages to build results based on AST tree layout.
Beta Was this translation helpful? Give feedback.
All reactions