Issue #21535 has been updated by byroot (Jean Boussier). Backport changed from 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN to 3.2: DONTNEED, 3.3: DONTNEED, 3.4: REQUIRED I ran a bisect and as suspected this regression was caused by the forward call optimization in https://github.com/ruby/ruby/commit/cdf33ed5f37f9649c482c3ba1d245f0d80ac01ce FYI: @tenderlovemaking ---------------------------------------- Bug #21535: `NoMethodError` becomes `NameError`when using `...` delegation and method call indirection https://bugs.ruby-lang.org/issues/21535#change-114248 * Author: Earlopain (Earlopain _) * Status: Open * ruby -v: ruby 3.5.0dev (2025-08-08T02:57:23Z master 3ad26d0501) +PRISM [x86_64-linux] * Backport: 3.2: DONTNEED, 3.3: DONTNEED, 3.4: REQUIRED ---------------------------------------- Consider this code: ```rb class Test def foo(...) nil.foo(...) end def foo_indirect foo end end begin Test.new.foo rescue => e puts e.class end begin Test.new.foo_indirect rescue => e puts e.class end ``` ```sh $ ruby -v foo.rb ruby 3.3.6 (2024-11-05 revision 75015d4c1f) [x86_64-linux] NoMethodError NoMethodError $ ruby -v foo.rb ruby 3.5.0dev (2025-08-08T02:57:23Z master 3ad26d0501) +PRISM [x86_64-linux] NoMethodError NameError ``` On ruby 3.3 it used to always raise a `NoMethodError`. Starting with Ruby 3.4, it raises a `NoMethodError` when calling the method directly, and a `NameError` when the method is called indirectly via a different method. The context is the `delegate` method from rails (original issue https://github.com/rails/rails/issues/55463), which rescues the `NoMethodError` to raise a more specific error class. The problem is the `...` delegation. If the method accepts no arguments, `*, **`, or something else, it behaves as expected. -- https://bugs.ruby-lang.org/