Project

General

Profile

Bug #10994

Inconsistent behavior when mixing optional argument and keyword splat

Added by ruipserra (Rui Serra) almost 5 years ago. Updated 5 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
ruby -v:
ruby 2.2.1p85 (2015-02-26 revision 49769) [x86_64-darwin13]
[ruby-core:<unknown>]

Description

The following code produces inconsistent behavior:

def foo(x=nil, **kw) 
  x 
end

h = { "a" => 1 }

foo(h)                  # => {"a"=>1} 
foo(h).equal?(h)        # => false
foo(h, y: 1).equal?(h)  # => true

It seems that in this very specific case, foo is returning a copy of h instead of returning h itself. I guess this is an edge case in the keyword extraction process.

Thank you for your time.


Related issues

Related to Ruby master - Feature #14183: "Real" keyword argumentClosedActions

History

#1

Updated by jeremyevans0 (Jeremy Evans) 7 months ago

Updated by jeremyevans0 (Jeremy Evans) 5 months ago

  • Status changed from Open to Closed

With the acceptance of #14183, you now get:

foo(h) 
# => {"a"=>1}

foo(h).equal?(h)
# => true

foo(h, y: 1).equal?(h) 
# => true

Also available in: Atom PDF