Skip to content

Wiki: Futures are Expensive to Compose #123

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.

Sign up for GitHub

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

Jump to bottom
Closed
tobnee opened this issue Feb 6, 2013 · 2 comments
Closed

Wiki: Futures are Expensive to Compose #123

tobnee opened this issue Feb 6, 2013 · 2 comments

Comments

@tobnee
Copy link

tobnee commented Feb 6, 2013

I think you refer to java.concurrent.Future and not other future implementations for the JVM.

Scala Futures for example have very similar goals and work just fine, without the hassle of j.c.Future. The wiki should therefore not claim that futures in general are "Expensive to Compose".
@benjchristensen
Copy link
Member

Yes, you are correct, Scala Futures support composition and callback hooks. The wiki and blog post were referring to Java Futures, not any other JVM language or library implementation.

I'll review changes to wording, perhaps to "Java Futures" instead of the more generic "Futures".

@benjchristensen
Copy link
Member

I have updated the wiki to state "Java Futures".

https://github.com/Netflix/RxJava/wiki

jihoonson pushed a commit to jihoonson/RxJava that referenced this issue Mar 6, 2020
@RobWin
* added circuitbreaker configs to ratpack module
4e9ddc3 
* added ratelimiter configs to ratpack module
* added retry configs to ratpack module

closes ReactiveX#123
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tobnee @benjchristensen