-
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
OperatorConcat #1074
OperatorConcat #1074
Conversation
RxJava-pull-requests #987 FAILURE |
RxJava-pull-requests #988 SUCCESS |
final NotificationLite<Observable<? extends T>> nl = NotificationLite.instance(); | ||
@Override | ||
public Subscriber<? super Observable<? extends T>> call(final Subscriber<? super T> child) { | ||
final SerializedSubscriber<T> s = new SerializedSubscriber<T>(child); |
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.
Since concat
is only ever subscribed to one Observable
at a time, do we actually need to do serialization?
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, because the outer observable can emit onError while the inner is running.
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.
Ah, it's the error case. Thanks!
I am merging despite having the question about serialization as that's an optimization question. |
Operator Concat
Issue #1060