ruby.git/test/prism, branch v4.0.2

[ruby/prism] Fix in handling

2026-03-06T17:02:23+00:00

in is a unique keyword because it can be the start of a clause or
an infix keyword. We need to be explicitly sure that even though in
_could_ close an expression context (the body of another in clause)
that we are not also parsing an inline in. The exception is the
case of a command call, which can never be the LHS of an expression,
and so we must immediately exit.

[Bug #21925]
[Bug #21674]

https://github.com/ruby/prism/commit/20374ced51

[ruby/prism] Fix error message for block/lambda with `...` argument

2026-03-06T17:02:23+00:00

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] Correctly handle `and?` and similar on ruby 4.0

2026-03-06T17:02:23+00:00

It gets confused for syntax introduced in https://bugs.ruby-lang.org/issues/20925
But it actually should be a plain method call.
`!`/`?` are not valid as part of an identifier, methods
however allow them as the last character.

Fixes [Bug #21946]

https://github.com/ruby/prism/commit/5d80bc5e1a

Sync Prism to 1.8.0

2026-01-13T01:59:55+00:00

[ruby/prism] Reject `p(p a, &block => value)` and similar

2025-12-19T00:58:53+00:00

Redo of https://github.com/ruby/prism/pull/3669 with more tests

https://github.com/ruby/prism/commit/48b403ea79

[ruby/prism] Add Ruby 4.1 as a version specifier

2025-12-19T00:58:53+00:00

https://github.com/ruby/prism/commit/138db9ccc4

[ruby/prism] Fix assertions in location_test.rb

2025-12-19T00:58:53+00:00

* assert_raise's 2nd argument is the failure message,
  shown when the expected exception is not raised.
  It's not the expected message.
  See https://github.com/test-unit/test-unit/issues/347

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

[ruby/prism] Fix `%Q` with newline delimiter and heredoc interpolation

2025-12-04T14:50:46+00:00

The lexer did not jump to the `heredoc_end`, causing the heredoc end delimiter
to be parsed twice.

Normally the heredocs get flushed when a newline is encountered. But because
the newline is part of the string delimiter, that codepath is not taken.

Fixes [Bug #21758]

https://github.com/ruby/prism/commit/7440eb4b11

[ruby/prism] Clean up test excludes

2025-12-02T16:20:43+00:00

Mostly not having to list version-specific excludes when testing against ripper/parse.y

Also don't test new syntax additions against the parser gems. The version support
for them may (or may not) be expanded but we shouldn't bother while the ruby version
hasn't even released yet.
(ruby_parser translation is not versioned, so let as is for now)

I also removed excludes that have since been implemented by parse.y

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

[ruby/prism] Update unicode tables to match that of CRuby

2025-11-30T04:24:06+00:00

The unicode version has been updated upstream, which means new
codepoints mapped to alpha/alnum/isupper flags. We need to update
our tables to match.

I'm purposefully not adding a version check here, since that is
such a large amount of code. It's possible that we could include
different tables depending on a macro (like UNICODE_VERSION) or
something to that effect, but it's such a minimal impact on the
running of the actual parser that I don't think it's necessary.

https://github.com/ruby/prism/commit/78925fe5b6