Bug #10309: Unexpected keyword parameters becomes an additional mandatory parameter

• Status: Rejected
• Assignee: matz (Yukihiro Matsumoto)
• Target version: 2.2.0
• ruby -v: 2.2 to 2.0
• Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN

[ko1 (Koichi Sasada)]

Is it an intentional behaviour?

def foo a, b, c, k1: 1
  p [a, b, c, k1]
end

foo 1, 2, {k1: 3, k2: 4}
#=> [1, 2, {:k1=>3, :k2=>4}, 1]

foo 1, 2, k1: 3, k2: 4
#=> [1, 2, {:k1=>3, :k2=>4}, 1]

[ko1 (Koichi Sasada)]

• Status changed from Open to Rejected

Ah, I'm sorry. It is duplicated ticket (I can't find another ticket).
My misunderstanding.

[ko1 (Koichi Sasada)]

• Related to Bug #10142: named params don't always capture passed named args added