Issue #19134 has been updated by shugo (Shugo Maeda).
mame (Yusuke Endoh) wrote in #note-12:
I feel that only `&` is acceptable since a block
is implicitly passed. But I don't think `*` and `**` make sense inside `def foo(...)`.
Speaking of implicity of blocks, `def f; g(&); end` causes a syntax error, so it may
be better to allow it, or disallow `def f(...); g(&); end` in the future versions.
Anyway, I've fixed the behavior of `...` as described in #note-9.
----------------------------------------
Feature #19134: ** is not allowed in def foo(...)
https://bugs.ruby-lang.org/issues/19134#change-100678
* Author: shugo (Shugo Maeda)
* Status: Closed
* Priority: Normal
* Assignee: matz (Yukihiro Matsumoto)
* Target version: 3.2
----------------------------------------
`*` and `&` are allowed in the body of a method with `...` argument forwarding, but
`**` is not allowed.
```
def foo(...)
bar(*) # OK
baz(&) # OK
quux(**) # NG
end
```
Is it intended behavior?
It seems that parse.y has code like `#ifdef RUBY3_KEYWORDS`, and if RUBY3_KEYWORDS, `**`
will also be supported.
--
https://bugs.ruby-lang.org/