Merged
Conversation
|
RxJava-pull-requests #1004 FAILURE |
Member
There was a problem hiding this comment.
This is a really inefficient operator! The use case requires this behavior, but every single onNext will cause a new Observable, Subscriber, and CompositeSubscription. Not pretty.
Member
Author
There was a problem hiding this comment.
There are many operators that subscribe to an observable on each onNext call.
Member
There was a problem hiding this comment.
Oh I know ... I just wish I could think of a way to make it less expensive!
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Operator Debounce again with improvements as discusssed in #1075
For Issue #1060