-
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: SequenceEqual #76
Comments
Looking at these implementations it seems that by using zip it will emit a sequence of true/false values rather than a single boolean specifying if the entire sequence is true/false. I think it is supposed to emit only a single value based on reading the MSDN docs. @mairbek If you re-read the docs, is it supposed to be a single value, or sequence of values emitted? If single, can you submit a fix? Probably a reduce type function that keeps going until it finds a false otherwise if it hits onComplete/onError the same on both sides it returns true. |
@benjchristensen okay, I'll submit the patch. |
Reduce doesn't seems to be a good choice in this case since it would wait for all pairs of events, even if first two were different. I will start by implementing All Operation #21 and applying it to a |
Okay, thanks. |
This happens to be more complicated that I've expected. I've come up with a test case that fails on @Test
public void testSequenceEqual3() {
Observable<Integer> first = Observable.toObservable(1, 2);
Observable<Integer> second = Observable.toObservable(1, 2, 3);
@SuppressWarnings("unchecked")
Observer<Boolean> result = mock(Observer.class);
sequenceEqual(first, second).subscribe(result);
verify(result, times(1)).onNext(false);
verify(result, times(1)).onCompleted();
verifyNoMoreInteractions(result);
} |
These should be public as part of issue ReactiveX#76
Done. |
…uitbreaker Migrated cpilsworth/retrofit-circuitbreaker to the resilience4j project
http://msdn.microsoft.com/en-us/library/hh229024(v=vs.103).aspx
http://msdn.microsoft.com/en-us/library/hh212108(v=vs.103).aspx
The text was updated successfully, but these errors were encountered: