ruby.git/prism/config.yml, branch v4.0.4 The Ruby Programming Language [ruby/prism] Fix error message for block/lambda with `...` argument 2026-03-06T17:02:23+00:00 Earlopain 14981592+Earlopain@users.noreply.github.com 2026-02-27T10:51:22+00:00 e7d2828fb677874fb425e6129e0c4c20acc0e1dd They currently complain that the parent method is not forwarding. But the actual problem is that these types of arguments simply don't accept `...` Fixes [Bug #21927] https://github.com/ruby/prism/commit/0aa2363331 
They currently complain that the parent method is not forwarding.
But the actual problem is that these types of arguments simply don't
accept `...`

Fixes [Bug #21927]

https://github.com/ruby/prism/commit/0aa2363331
[ruby/prism] Revert "Fix invalid Ruby code example in ClassNode comment" 2025-11-29T21:00:53+00:00 Kevin Newton kddnewton@gmail.com 2025-11-29T20:51:06+00:00 e3bc1852b3a7bcacf3e18d1644fbea7839abe019 https://github.com/ruby/prism/commit/b960079559 
https://github.com/ruby/prism/commit/b960079559
[ruby/prism] Fix label interpolated string 2025-11-29T19:48:30+00:00 Kevin Newton kddnewton@gmail.com 2025-11-29T19:28:36+00:00 7c2eb946e04940901ee1957c3fb43897c661568e https://github.com/ruby/prism/commit/e3e2b1ed04 
https://github.com/ruby/prism/commit/e3e2b1ed04
[ruby/prism] Fix invalid Ruby code example in ClassNode comment 2025-11-28T15:38:40+00:00 qraqras q100rrraaa@gmail.com 2025-11-28T00:58:38+00:00 8eaefd93951143661b1f515a8c9cda12263d2b56 https://github.com/ruby/prism/commit/5b7456c8f6 
https://github.com/ruby/prism/commit/5b7456c8f6
[ruby/prism] Add docs for super nodes 2025-11-19T02:01:57+00:00 Alexander Momchilov alexander.momchilov@shopify.com 2025-11-14T15:14:44+00:00 1979f8c07d6c2794dda7b482372c9dc0e9f305b0 https://github.com/ruby/prism/commit/69abcdbb18 
https://github.com/ruby/prism/commit/69abcdbb18
Handle deeply nested capture variables syntax err 2025-11-17T02:30:24+00:00 Kevin Newton kddnewton@gmail.com 2025-11-16T21:57:42+00:00 8d0105824f1cf722c1319496ed903b6a18efdafe When there are nested capture variables inside of a pattern match that has an alternation pattern, it is a syntax error. Currently it only adds a syntax error when it is at the top level of the pattern. 
When there are nested capture variables inside of a pattern match
that has an alternation pattern, it is a syntax error. Currently it
only adds a syntax error when it is at the top level of the pattern.
[ruby/prism] Reject endless method as a block parameter default 2025-11-14T16:27:38+00:00 Earlopain 14981592+Earlopain@users.noreply.github.com 2025-11-03T11:24:38+00:00 bec69617a00e1d98748b319411f221568a4b6c66 Fixes [Bug #21661] https://github.com/ruby/prism/commit/475fa46a82 
Fixes [Bug #21661]

https://github.com/ruby/prism/commit/475fa46a82
[Feature #21572] Syntax error at capture in alternation pattern 2025-11-14T12:03:04+00:00 Nobuyoshi Nakada nobu@ruby-lang.org 2025-10-23T15:57:26+00:00 f4b6a5191ceb0ed0cd7a3e3c8bab24cc0dd15736 Should fail even with `-c` option. 
Should fail even with `-c` option.
[ruby/prism] Add equal_loc to call nodes 2025-10-30T13:06:09+00:00 Kevin Newton kddnewton@gmail.com 2025-10-26T20:16:41+00:00 8e7d427a721ab715361c577fdea94fdebece6c6d In the case of attribute writes, there are use cases where you want to know the location of the = sign. (Internally we actually need this for translation to the writequark AST.) https://github.com/ruby/prism/commit/bfc798a7ec 
In the case of attribute writes, there are use cases where you want
to know the location of the = sign. (Internally we actually need
this for translation to the writequark AST.)

https://github.com/ruby/prism/commit/bfc798a7ec
[ruby/prism] For these special cases, there exists no optional argument type. Since a endless method is started with `=`, there was ambiguity here. We have to simply reject these in all cases. 2025-10-08T13:04:57+00:00 Earlopain 14981592+Earlopain@users.noreply.github.com 2025-10-08T12:54:14+00:00 b8f8d646a64f883652b44780c4174a85f98d1c82 This adds a new error for the following reason: * `def foo arg = nil` is interpreted as a normal method call with optional `arg` without matching `end` * `def foo *arg = nil; end` is interpreted as a endless method call that has body `nil` with extraneous `end` `def foo *arg = nil` is somewhere inbetween and I don't know how to otherwise indicate the error. Now the second case above also shows the newly added error message. Fixes [Bug #21623] https://github.com/ruby/prism/commit/e1910d4492 
This adds a new error for the following reason:
* `def foo arg = nil` is interpreted as a normal method call with optional `arg` without matching `end`
* `def foo *arg = nil; end` is interpreted as a endless method call that has body `nil` with extraneous `end`

`def foo *arg = nil` is somewhere inbetween and I don't know how to otherwise indicate the error.
Now the second case above also shows the newly added error message.

Fixes [Bug #21623]

https://github.com/ruby/prism/commit/e1910d4492