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
Fix Promise#then
.
#729
Fix Promise#then
.
#729
Conversation
Hi, thanks for the fix. However the docs need to be fixed instead at the moment. The change as is would be backward incompatible. (Even though I would also like to use named arguments.) |
Maybe we could support both in order to not break compatibility? |
yeah, that's a good plan, however concurrent-ruby has to drop support for 1.9 officially first to be able to do it. So I won't be able to merge this PR until before next minor release. |
Why? There are other methods using named parameters. |
@pitr-ch, ping. |
Sorry I was away. I think they are using last argument as an options Hash, named arguments should not be used. If you saw named arguments please point me to it. |
Yes, I just meant that they can be used with named parameters, not that they are implemented with them. Anyways, I implemented it to support both the current version and the version with an option Hash/named parameter. |
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.
Thanks again!
The docs say it should work like
then(executor: executor)
.