New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor - #2812 iterable separate performance #2815
Merged
nomisRev
merged 5 commits into
arrow-kt:main
from
Khepu:refactor/2812-iterable-separate-performance
Sep 12, 2022
Merged
Changes from 4 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
20a8967
Refactor: Use fold to separate Iterable of Either
Khepu f9b32aa
Refactor: Use fold to separate Iterable of Validated
Khepu de16de1
Merge branch 'main' into refactor/2812-iterable-separate-performance
Khepu a7d8283
Merge branch 'main' into refactor/2812-iterable-separate-performance
nomisRev 3690520
Refactor: Implementation closer to STD
Khepu File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we use
mutableListOf
here and useadd
inside of thefold
body? That would avoid having to recreatePair
on every element of theList
. The returned type can still be read-onlyList
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It can also be rewritten to
while
if we'd pattern similar to Kotlin Std implementations.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This eliminates List.size allocations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think mimicking the Kotlin stdlib is a good way to go. Looking at the implementation it's gonna be a lot like this (based on
map
):If that is something we are happy with, let me know!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that looks perfect to me @Khepu!