Suggestion: Split or Unify BodyVisitor and SymbolTableVisitor
Came up as a possible idea today during the meeting. Splitting them up might make it easier to debug. Some
visitors are rather similar, so further unification within the same file might be in order as well. The MR associated would be very trivial, but it'd be good to hear from everyone beforehand.
To clarify, this issue is meant to solicit opinions on the following options:
- A. Keep as is --> Both visitor classes in the same file
- B. Split --> Each visitor class gets its own file
- C. Attempt to unify --> Merge logic so the same visitor can work for both Body and Symboltable when possible