Bug #11586: Weird keyword argument behavior

• Status: Closed
• Assignee: -
• Target version: -
• ruby -v: ruby 2.2.1p85 (2015-02-26 revision 49769) [i386-mingw32]
• Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN

[ChazDomerese (Chaz Domerese)]

Writing a dynamic method caller, I ran into an issue with splatting in both normal and keyword arguments. When running the following code that is attached, the results suggest the key2 argument is nil, but it should equal "true"? This seems to apply only to 2.2.1, as the code attached works on both Windows and Linux, Ruby versions 2.1.6, and 2.2.3. It seems that 2.2.1 is the culprit here. Will this fix be resolved in 2.2.1?

[nobu (Nobuyoshi Nakada)]

• Status changed from Open to Closed

It has been fixed in 2.2 already.