From: "jeremyevans0 (Jeremy Evans)" Date: 2022-04-04T23:05:15+00:00 Subject: [ruby-core:108172] [Ruby master Bug#18673] Anonymous block forwarding fails when combined with keyword arguments Issue #18673 has been updated by jeremyevans0 (Jeremy Evans). Backport changed from 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN to 2.7: DONTNEED, 3.0: DONTNEED, 3.1: REQUIRED I submitted a pull request to fix this issue: https://github.com/ruby/ruby/pull/5761 ---------------------------------------- Bug #18673: Anonymous block forwarding fails when combined with keyword arguments https://bugs.ruby-lang.org/issues/18673#change-97146 * Author: brasic (Carl Brasic) * Status: Open * Priority: Normal * Backport: 2.7: DONTNEED, 3.0: DONTNEED, 3.1: REQUIRED ---------------------------------------- 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: