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.
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
Avoid storing more transformed elements than necessary #3376
Avoid storing more transformed elements than necessary #3376
Changes from 3 commits
2893b3a
6d23219
5d1ccda
a035cbf
244a6c7
eabe74b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Nit: Do we really need two lambdas here? 🤔
Or was that for
JvmName
? Otherwise I am also fine usingforEachAccumulatingImpl
or something. I've started doing that in my own projects, similar how to KotlinX Coroutines does this withproduceImpl
.flattenMergeImpl
, etc.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.
We do, because we still need to call
transform
on each value, just not add the result to the list.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.
Why not have:
and simply we only call
add
if we don't have any errors.We could also just have a
Boolean
parameter instead, with similar effects.I really also dislike the binary-size blowup that can occur because
mapOrAccumulate
inlines its block in 2 different places.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.
Nit: same as above, but with
error.isEmpty()