-
Notifications
You must be signed in to change notification settings - Fork 111
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
A better name of collect
#63
Comments
I'll probably also prefer to have another name for the RxJava |
Any suggestion for the name? @samuelgruetter @headinthebox @jbripley |
Maybe |
I think finally we should change
Adding RxJava For Should we keep the current improper signatures and add a method to give users alternative option, or fix them? |
I don't agree on this, because |
Due to project EOL status, this improvement will not be made. |
RxJava changed
collect
toObservable<R> collect(Func0<R> stateFactory, final Action2<R, ? super T> collector)
in https://github.com/ReactiveX/RxJava/pull/1884/files#diff-c3bbc6e9e497930d46361b0b8140431cR3471 to fix ReactiveX/RxJava#1831RxScala has the same issue and needs a similar operator too. ReactiveX/RxJava#1835 is a great fix for RxScala but has an ambiguity issue: ReactiveX/RxJava#1884
To solve this issue, here are 3 options:
Add
collect
into RxScala to call RxJava'scollect
. However, RxScala has a same name method:def collect[R](pf: PartialFunction[T, R]): Observable[R]
. It may confuse people because they are totally different.Change
foldLeft
tocollect
.I prefer 3). Any suggestion for the new name?
The text was updated successfully, but these errors were encountered: