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
Feature: TransformOnObservable Operator for SourceCache #841
Feature: TransformOnObservable Operator for SourceCache #841
Changes from 3 commits
a5c0a98
36e2c65
d489f51
aff08bb
87ce8e3
9f35d67
ac4c2f8
73ee7da
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.
I think the concept of an update counter to batch results is inspired. The same concept would probably benefit several other operations.
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.
Thank you! 😊
I used it for
TransformManyAsync
to get behavior similar toTransformMany
after you stressed the importance of minimizing the number of ChangeSets. I was also thinking that it might be beneficial to use in other places, so I'll keep a lookout for those.There is some nuance to using it. For example, you have to increment the counter before the
Synchronize
so that updates coming in on other threads are counted and the emission downstream is deferred until it can be handled.There are also some downsides: