-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Operator GroupBy Pull Request - Review and Refactor #179
Operator GroupBy Pull Request - Review and Refactor #179
Conversation
RxJava-pull-requests #18 SUCCESS |
The only thing I don't like right now about this is having GroupedObservable in the rx.* package. It feels like an implementation detail that should live in a sub-package rather than the top-most package. For example, in Rx.Net I'm wondering if we should have rx.observables similar to rx.subscriptions (#173). Observable belongs at rx.Observable (and maybe the rx.Subscription interface as well) but all other impls should be in a sub-package I think. |
Operator GroupBy Pull Request - Review and Refactor
RxJava-pull-requests #19 SUCCESS |
Operator GroupBy Pull Request - Review and Refactor
Refactored version of pull request #176 for issue #51
I would like to avoid delegation if possible since it will mean it needs to be kept in sync with Observable.
This refactored approach allows inheritance without delegation by composing the Observable inside another operator function.