From: meanlogin@...
Date: 2014-09-25T16:52:55+00:00
Subject: [ruby-core:65271] [ruby-trunk - Bug #10142] named params don't always capture passed named args

Issue #10142 has been updated by First Last.


another example of how this creates surprise, confusion and subtle bugs

def foo(a = 1, **options)
end

foo opt: 2
_____________

if 'a' becomes mandatory, instead of raising, "a" will absorb the options, which is clearly something no one would ever expect or want, when you have "**" specifically designed for this purpose

so why is the current behavior preferable?

----------------------------------------
Bug #10142: named params don't always capture passed named args
https://bugs.ruby-lang.org/issues/10142#change-49095

* Author: First Last
* Status: Rejected
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
~~~ruby
irb(main):007:0> def foo(a, b: nil); [a, b] end
:foo
irb(main):008:0> foo b: 1
[
  [0] {
    :b => 1
  },
  [1] nil
]
~~~
______________________________

would be better if this raised



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