Bug #20720: prism incorrectly marks SuperNode as forwarding in some cases

• Status: Closed
• Assignee: -
• Target version: -
• ruby -v: 3.4.0dev
• Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN

[luke-gru (Luke Gruber)]

class A
  def foo(*b, &block)
  end
end

class B < A
  def foo(...)
    super()
    puts "2"
  end
end

results in:

./ruby --parser=prism -I../ruby/lib -I. -I.ext/x86_64-linux -I.ext/common -r./x86_64-linux-fake ../ruby/test.rb

-- raw disasm--------

   trace: 8

   trace: 1

 <L000> [sp: 0, unremovable: 0, refcnt: 0]

   0000 putself                                                          ( 284)

   0001 invokesuperforward   <calldata:, 0>, nil                         ( 284)

*  0004 pop                                                              ( 284)

   trace: 1

   0005 putself                                                          ( 285)

   0006 putchilledstring     "2"                                         ( 285)

   0008 opt_send_without_block <calldata:puts, 1>                        ( 285)

   trace: 10

   0010 leave                                                            ( 286)

---------------------

../ruby/test.rb: ../ruby/test.rb:284: argument stack underflow (-1) (SyntaxError)

It should differentiate between forwarding nodes and non-ZSUPER Super nodes with no arguments.

[luke-gru (Luke Gruber)]

• Description updated (diff)

[luke-gru (Luke Gruber)]

PR here: https://github.com/ruby/ruby/pull/11565

[luke-gru (Luke Gruber)]

• Status changed from Open to Closed

Applied in changeset git|5d358b660d41e64de301f428dc0300a52a6f9566.

---

Fix issue with super and forwarding arguments in prism_compile.c

Fixes [Bug #20720]