Optimize traverse_and_update without accumulator #584
Merged
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.
Today
traverse_and_update/2
calls the same traverse functions astraverse_and_update/3
, so the traverse keeps creating a bunch of tuples to store the accumulator value unnecessarily.This PR optimizes
traverse_and_update/2
by avoiding this tuples, it required basically duplicating the traverse functions, since the implementation is small it shouldn't be an issue.