Skip to content
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

Flowable.reduce(BiFunction) does not signal NoSuchElementException #6195

Closed
akarnokd opened this issue Sep 3, 2018 · 0 comments

Comments

@akarnokd
Copy link
Member

commented Sep 3, 2018

The JavaDocs of Flowable.reduce(BiFunction) incorrectly mentions that an empty source results in a NoSuchElementException. It returns a Maybe thus an empty source will result in an empty Maybe. The Observable.reduce(BiFunction) counterpart has the correct text.

The "If the source is empty, a NoSuchElementException is signaled." should be removed.

@akarnokd akarnokd added this to the 2.2 backlog milestone Sep 3, 2018
@akarnokd akarnokd added the PR welcome label Sep 3, 2018
ylecaillez added a commit to ylecaillez/RxJava that referenced this issue Sep 3, 2018
Empty source does not signal NoSuchElementException.
ylecaillez added a commit to ylecaillez/RxJava that referenced this issue Sep 3, 2018
Empty source does not signal NoSuchElementException.
akarnokd added a commit that referenced this issue Sep 3, 2018
Empty source does not signal NoSuchElementException.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.