Ruby Issue Tracking System

02/23/2016

10:26 AM Ruby Bug #12104: Procs keyword arguments affect value of previous argument

Looking deeper now it seems to be that this is because the first argument is an Array and that when that happens it's interpreting that as the elements of the array being the arguments of the Proc. Is that supposed to happen? cheerfulstoic (Brian Underwood)

10:19 AM Ruby Bug #12104: Procs keyword arguments affect value of previous argument

This seems to also happen when trying to use a options Hash as the second argument:
~~~
2.3.0 :009 > p = Proc.new {|nodes, options = {}| puts nodes.inspect }
=> #<Proc:0x007fa52b13b348@(irb):9>
2.3.0 :010 > p.call([])
nil
=> ni... cheerfulstoic (Brian Underwood)

10:15 AM Ruby Bug #12104 (Rejected): Procs keyword arguments affect value of previous argument

This seems like a bug to me:
~~~
2.3.0 :001 > p = Proc.new {|nodes, match_array: false| puts nodes.inspect }
=> #<Proc:0x007fa52c0659e0@(irb):1>
2.3.0 :002 > p.call([])
nil
=> nil
2.3.0 :003 > p.call([], match_array: true)
[... cheerfulstoic (Brian Underwood)