Optimize logical nodes visit methods. #166
Open
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.
This commit provides memory optimization when visiting
LogicalNode
's children. Old implementation was invokingLogicalNode#getChildren
which makes shallow copy of its children nodes to only iterate over it we can use the fact thatLogicalNode
is in factjava.lang.Iterable
and use enhanced for loop to iterate over it. Using it that way is more memory efficient and does not involve shallow copying because iterator returned byLogicalNode
is unmodifiable.