Issue #8316 has been updated by Andrew Vit.

Backport deleted (1.9.3: UNKNOWN, 2.0.0: UNKNOWN)

Andrew Schwartz wrote:
> This is unfortunately still an issue with default values in positional arguments

See #11967 for the explanation.

----------------------------------------
Bug #8316: Can't pass hash to first positional argument; hash interpreted as keyword arguments
https://bugs.ruby-lang.org/issues/8316#change-56806

* Author: Tyler Rick
* Status: Closed
* Priority: Normal
* Assignee: Yusuke Endoh
* ruby -v: ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-darwin13]
* Backport: 
----------------------------------------
I'm able to pass any other type of object to my first argument:

 def foo(hash, opt: true)
   puts "hash: #{hash}, opt: #{opt.inspect}"
 end
 
 foo 'a'                 # => hash: a, opt: true
 foo [{a:1}]             # => hash: [{:a=>1}], opt: true
 foo [{a:1}], opt: false # => hash: [{:a=>1}], opt: false

But when I try to pass a hash, it raises an ArgumentError:

 foo({a:1})  # Raises ArgumentError: unknown keyword: a
 # Expected behavior: hash: {:a=>1}, opt: true

I tried to work around the "unknown keyword" error by using ** but ended up getting a "wrong number of arguments (0 for 1)" error instead.

 def foo_with_extra(hash, **extra)
   puts "hash: #{hash}, extra: #{extra.inspect}"
 end
 
 foo_with_extra 'a'                 # hash: a, extra: {}
 foo_with_extra [{a:1}]             # hash: [{:a=>1}], extra: {}
 foo_with_extra [{a:1}], opt: false # hash: [{:a=>1}], extra: {:opt=>false}
 
 foo_with_extra({a:1})  # Raises ArgumentError: wrong number of arguments (0 for 1)
 # Expected behavior: hash: {:a=>1}, extra: {}

This behavior is surprising and I haven't seen it mentioned anywhere before. Is it really intentional?



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

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>