From: daniel@...42.com Date: 2019-09-05T01:57:40+00:00 Subject: [ruby-core:94783] [Ruby master Feature#14183] "Real" keyword argument Issue #14183 has been updated by Dan0042 (Daniel DeLorme). @jeremyevans0 wrote: > You do not need to have two separate definitions of `method_missing`, unless you want to be backwards compatible with 1.9 (which doesn't support `**` for keyword parameters). You should always use `*a, **o, &b` when forwarding. Example: Counter-example: ```ruby class B def initialize(x) @x = x end def method_missing(*a, **o, &b) @x.send(*a, **o, &b) end end class C def initialize(x) @x = x end def method_missing(*a, &b) @x.send(*a, &b) end end class D def method_missing(*a, &b) [*a, b] end end b = B.new(D.new) c = C.new(D.new) b.a == c.a # false in 2.6 / true in 2.7 b.a(1) == c.a(1) # false in 2.6 / true in 2.7 b.a(a: 1) == c.a(a: 1) # true / b.a warns in 2.7 b.a({a: 1}) == c.a({a: 1}) # true / b.a warns in 2.7 b.a({a: 1}, **(;{})) == c.a({a: 1}, **(;{})) # true ``` ---------------------------------------- Feature #14183: "Real" keyword argument https://bugs.ruby-lang.org/issues/14183#change-81400 * Author: mame (Yusuke Endoh) * Status: Closed * Priority: Normal * Assignee: * Target version: Next Major ---------------------------------------- In RubyWorld Conference 2017 and RubyConf 2017, Matz officially said that Ruby 3.0 will have "real" keyword arguments. AFAIK there is no ticket about it, so I'm creating this (based on my understanding). In Ruby 2, the keyword argument is a normal argument that is a Hash object (whose keys are all symbols) and is passed as the last argument. This design is chosen because of compatibility, but it is fairly complex, and has been a source of many corner cases where the behavior is not intuitive. (Some related tickets: #8040, #8316, #9898, #10856, #11236, #11967, #12104, #12717, #12821, #13336, #13647, #14130) In Ruby 3, a keyword argument will be completely separated from normal arguments. (Like a block parameter that is also completely separated from normal arguments.) This change will break compatibility; if you want to pass or accept keyword argument, you always need to use bare `sym: val` or double-splat `**` syntax: ``` # The following calls pass keyword arguments foo(..., key: val) foo(..., **hsh) foo(..., key: val, **hsh) # The following calls pass **normal** arguments foo(..., {key: val}) foo(..., hsh) foo(..., {key: val, **hsh}) # The following method definitions accept keyword argument def foo(..., key: val) end def foo(..., **hsh) end # The following method definitions accept **normal** argument def foo(..., hsh) end ``` In other words, the following programs WILL NOT work: ``` # This will cause an ArgumentError because the method foo does not accept keyword argument def foo(a, b, c, hsh) p hsh[:key] end foo(1, 2, 3, key: 42) # The following will work; you need to use keyword rest operator explicitly def foo(a, b, c, **hsh) p hsh[:key] end foo(1, 2, 3, key: 42) # This will cause an ArgumentError because the method call does not pass keyword argument def foo(a, b, c, key: 1) end h = {key: 42} foo(1, 2, 3, h) # The following will work; you need to use keyword rest operator explicitly def foo(a, b, c, key: 1) end h = {key: 42} foo(1, 2, 3, **h) ``` I think here is a transition path: * Ruby 2.6 (or 2.7?) will output a warning when a normal argument is interpreted as keyword argument, or vice versa. * Ruby 3.0 will use the new semantics. ---Files-------------------------------- vm_args.diff (4.19 KB) vm_args_v2.diff (4.18 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: