Issue #10699 has been updated by Tomoyuki Chikanaga.

Backport changed from 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN to 2.0.0: UNKNOWN, 2.1: REQUIRED, 2.2: UNKNOWN

Thank you akr san for your consideration about backports.
I'll fill Backport field with 2.1: REQUIRED only for r49173.

----------------------------------------
Bug #10699: m(*a, **b) doesn't recognize integer options.
https://bugs.ruby-lang.org/issues/10699#change-50860

* Author: Akira Tanaka
* Status: Feedback
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: ruby 2.3.0dev (2015-01-06 trunk 49159) [x86_64-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: REQUIRED, 2.2: UNKNOWN
----------------------------------------
It seems a method defined as m(*a, **b) doesn't recognize integer options.

```
% ./ruby -v -e '
def m(*a, **b)
  p [a, b]
end
m(1, 2 => 3)
m(1, :foo => 3)
'
ruby 2.3.0dev (2015-01-06 trunk 49159) [x86_64-linux]
[[1, {2=>3}], {}]
[[1], {:foo=>3}]
```

I think the result should be follows.

```
[[1], {2=>3}]
[[1], {:foo=>3}]
```

I found this problem by https://github.com/ruby/ruby/pull/808




-- 
https://bugs.ruby-lang.org/