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

RxScala mergeMap and concatMap bindings missing #1251

Closed
headinthebox opened this issue May 22, 2014 · 6 comments
Closed

RxScala mergeMap and concatMap bindings missing #1251

headinthebox opened this issue May 22, 2014 · 6 comments
Assignees
Labels
Milestone

Comments

@headinthebox
Copy link
Contributor

Bindings for mergeMap and concatMap are missing in RxScala.

My proposal is to merge mergeMap and flatMap.

@headinthebox headinthebox added this to the 0.19 milestone May 22, 2014
@headinthebox headinthebox self-assigned this May 22, 2014
@benjchristensen
Copy link
Member

@zsxwing Can you get these in soon before 0.19? Otherwise we can pick them up in 0.19.1.

By the way, mergeMap was created as an alias after discussion with you when we created concatMap and switchMap. The idea was to have "map" functions for each of merge, concat, and switch, but that flatMap is the term everyone uses for mergeMap so both would exist.

It seems you feel differently now? Should we deprecate mergeMap in rxjava-core and remove it when we hit 1.0RC?

@headinthebox
Copy link
Contributor Author

Totally inconsistent I know, but I like to have all the aliases in RxJava core, but for the Scala bindings it feels more natural to only have flatMap and drop the mergeMap alias. But as I say, this is totally irrational ;-) and I would be OK to have all.

@zsxwing
Copy link
Member

zsxwing commented Jun 2, 2014

@zsxwing Can you get these in soon before 0.19? Otherwise we can pick them up in 0.19.1.

@benjchristensen this one will not be a breaking change in RxScala. So both are good to me.

@headinthebox
Copy link
Contributor Author

@zsxwing Any preference? We can always add mergeMap later, but once we put it in as an alias for flatMap it is in forever.

@jbripley
Copy link
Contributor

jbripley commented Jun 2, 2014

Speaking as a user of RxScala and Scala, I would say just to have flatMap, since that's what a Scala user would expect. Anything inherit in the missing mergeMap functions that would make that confusing?

@zsxwing
Copy link
Member

zsxwing commented Jun 2, 2014

@headinthebox I mean now there is only a flatMap method in RxScala, so we can add other methods to RxScala at any time without breaking anything. Never mind. Already sent a PR to add them, #1304

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants