ruby.git/prism/templates/src/diagnostic.c.erb, branch v4.0.2 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
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] 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
[ruby/prism] Improve error handling for missing parentheses after 'not' in command calls 2025-08-05T17:58:09+00:00 ydah t.yudai92@gmail.com 2025-07-07T10:06:26+00:00 087190fcd21973eb34b600fa82e6567189f4bbd7 https://github.com/ruby/prism/commit/d9151b8a82 
https://github.com/ruby/prism/commit/d9151b8a82
[ruby/prism] Reject `true && not true` 2025-08-05T17:58:09+00:00 Yusuke Endoh mame@ruby-lang.org 2025-06-13T03:44:08+00:00 f814a777550ee39865f8fe26d0061cba8b715509 A command-call-like `not true` must be rejected after `&&` and `||`. https://bugs.ruby-lang.org/issues/21337 https://github.com/ruby/prism/commit/0513cf22ad 
A command-call-like `not true` must be rejected after `&&` and `||`.

https://bugs.ruby-lang.org/issues/21337

https://github.com/ruby/prism/commit/0513cf22ad
[ruby/prism] Improve error handling for missing parentheses after 'not' in command calls 2025-07-16T15:48:09+00:00 ydah t.yudai92@gmail.com 2025-07-07T10:06:26+00:00 4eb0a6cd4daa2ea53b53aa14d463040912c0838c https://github.com/ruby/prism/commit/d9151b8a82 
https://github.com/ruby/prism/commit/d9151b8a82
[ruby/prism] Reject `true && not true` 2025-07-16T15:48:09+00:00 Yusuke Endoh mame@ruby-lang.org 2025-06-13T03:44:08+00:00 4cf85fe2140d0522f924ab57c850b2f03b967390 A command-call-like `not true` must be rejected after `&&` and `||`. https://bugs.ruby-lang.org/issues/21337 https://github.com/ruby/prism/commit/0513cf22ad 
A command-call-like `not true` must be rejected after `&&` and `||`.

https://bugs.ruby-lang.org/issues/21337

https://github.com/ruby/prism/commit/0513cf22ad
Use a single quote instead of a backtick for error messages 2025-01-06T01:50:53+00:00 Junichi Ito jit@sonicgarden.jp 2024-12-22T03:54:35+00:00 c8e3d745fabc2060a6e5c7342c881bb31f58f5f5 Fix https://bugs.ruby-lang.org/issues/20977 
Fix https://bugs.ruby-lang.org/issues/20977