Prevent isempty(children(node)) from calling iterate (20% improvement in iteration speed) #122
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.
During some profileing I noticed the
isempty
test on children were causing a call tonext
theniterate
This remedies that buy replacing any call to
isempty(children(node))
with effectivelyischildrenempty(children(node))
which for the most part is just checking for the interface definition of empty which is an empty typle.The major culprit of the problem was
isempty(children(TreeCursor))
Benchmark code:
master benchmarks:
PR benchmarks