-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Different behaviors of SequenceEqual
in Rx.Net and RxJava
#564
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
Comments
I've noticed that using public static <T> Observable<Boolean> sequenceEqual(Observable<? extends T> first,
Observable<? extends T> second, Func2<? super T, ? super T, Boolean> equality) {
return zip(first, second, equality).all(Functions.<Boolean>identity());
} Using the materialized view is not an option as errors need to be propagated directly and not compared (and generally, equals doesn't work on Throwables). |
I can take this this weekend. |
fixed in #575 |
… support … (ReactiveX#564) * Issue ReactiveX#547: Adapted CircuitBreakerConfigurationProperties to support the new sliding window types.
Looks
SequenceEqual
in Rxjava is not correct.In Rx.Net,
SequenceEqual
returns an Observable which only has one element indicating if these two sequences are same. For example,Outputs:
But in RxJava, the following codes:
Output 100
true
s.The text was updated successfully, but these errors were encountered: