-
Notifications
You must be signed in to change notification settings - Fork 35
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
Removed futuroscope #133
Removed futuroscope #133
Conversation
71adb44
to
bb6d631
Compare
8e19b13
to
f90a92a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
UPGRADING.md
Outdated
end | ||
``` | ||
|
||
The default new behavior is synchronous. Include `futuroscope` in your `Gemfile` and wrap Hyperclient requests into `Futuroscope::Future.new` blocks when you wish to utilize this pattern. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
May I suggest we point people at concurrent-ruby
for the reasons I discussed on #123?
It's equivalent in this case is wrapping the request with Concurrent::Future.execute
.
I wrote this. I think that's what we want. The default new behavior is synchronous. We recommend concurrent-ruby for your future asynchronous needs. Include Just hit merge if you're happy with it ;) |
Merging away! |
Closes #123.
@ivoanjo Your call to merge!