From: "nagachika (Tomoyuki Chikanaga)" <noreply@...>
Date: 2022-06-18T07:38:37+00:00
Subject: [ruby-core:108996] [Ruby master Bug#18673] Anonymous block forwarding fails when combined with keyword arguments

Issue #18673 has been updated by nagachika (Tomoyuki Chikanaga).

Backport changed from 2.7: DONTNEED, 3.0: DONTNEED, 3.1: REQUIRED to 2.7: DONTNEED, 3.0: DONTNEED, 3.1: DONE

ruby_3_1 750d4dc3aff7c2fef25fe99f1b98327f68734c9a merged revision(s) 3bb70a6924ddd83f90b508b5bbc4d5629b8a41c6.

----------------------------------------
Bug #18673: Anonymous block forwarding fails when combined with keyword arguments
https://bugs.ruby-lang.org/issues/18673#change-98107

* Author: brasic (Carl Brasic)
* Status: Closed
* Priority: Normal
* Backport: 2.7: DONTNEED, 3.0: DONTNEED, 3.1: DONE
----------------------------------------
Hello!

I tried to use the anonymous block forwarding feature introduced in https://bugs.ruby-lang.org/issues/11256 and released with ruby 3.1.

Unfortunately it appears to unexpectedly fail during parsing when used in a method that also accepts keyword arguments.  I don't see this limitation documented so I presume it is a bug.  I've attached a simple reproduction script.

/cc @jeremyevans0 as author.

```
$ ruby -v
ruby 3.1.1p18 (2022-02-18 revision 53f5fc4236) [x86_64-linux]
$ ruby anon_repro.rb
anon_repro.rb:14: no anonymous block parameter
```


Carl

---Files--------------------------------
anon_repro.rb (223 Bytes)


-- 
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>