-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
possible Enumerable/Iterable .map bug #1199
Comments
It's because yielding multiple values doesn't mean yielding a tuple of those values. I don't consider this a bug. Also check this: #105 (comment) So I think this is a duplicate of #105, but please reopen if not |
BTW, Working version of provided code example: http://carc.in/#/r/bww Best Regards, 2015-08-19 0:58 GMT+02:00 Ary Borenszweig notifications@github.com:
|
Instead of |
@jhass yeah: http://carc.in/#/r/bwx Though parenthesis for |
I would like yield(a, b) to work with Enumerable AND map { |a, b| }. This issue similar but not identical to #105. The issue here is with Enumerable and the types that it accepts. I would like yield(a, b) to work with Enumerable AND map { |a, b| }.
Possible solutions:
|
When map is used the expected Enumerable type is incorrect. The bug seems to appear with any tuple types.
The same code also failed with Iterable/Iterator.
http://carc.in/#/r/bkv
The text was updated successfully, but these errors were encountered: