Optimize SyntaxVisitor
and make it a protocol
#77
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
shouldVisit
checks. They are unnecessary now.SyntaxVisitor
to a protocol.SyntaxVisitor
was a pure abstract class, a protocol is more appropriate for it.Syntax
/_SyntaxBase
during visitation to improve performanceSyntaxAnyVisitor
as separate protocol for clients that want to use avisitAny(_:Syntax)
function. It is a separate protocol because this kind of visitation is 1.6x slower.SyntaxVisitor.visitPre()
because it doesn't seem useful, a client can put related code intovisit()
instead.SyntaxVerifier
to a separate source fileAfter these changes, performance of visition has improved significantly. Depending on whether the
SyntaxVisitor
client was visiting only token nodes or all nodes, the speed-up is 5x or 6x respectively.