ruby.git/test/prism/fixtures, 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] 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

[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] 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] Revert "Reject `p(p a, &block => value)` and similar"

2025-11-23T21:36:19+00:00

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

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

2025-11-23T18:15:15+00:00

They were being parsed as `p((p a, &block) => value)`.
When we get to this point, we must not just have parsed a command call, always consuming the `=>` is not correct.

Closes [Bug #21622]

https://github.com/ruby/prism/commit/796ab0edf4

[ruby/prism] Reject endless method as a block parameter default

2025-11-14T16:27:38+00:00

Fixes [Bug #21661]

https://github.com/ruby/prism/commit/475fa46a82

[ruby/prism] Rename Ruby 3.5 to Ruby 4.0

2025-11-08T00:22:17+00:00

See https://github.com/ruby/ruby/commit/6d81969b475262aba251e99b518181bdf7c5a523

It leaves the old variant around. RuboCop for examples accesses `Prism::Translation::Parser35`
to test against ruby-head. For now I left these simply as an alias

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

[ruby/prism] Unescape unary method calls

2025-10-30T13:05:51+00:00

Followup to https://github.com/ruby/prism/pull/2213

Before:
```sh
$ ruby -ve "puts 42.~@"
ruby 3.4.6 (2025-09-16 revision https://github.com/ruby/prism/commit/dbd83256b1) +PRISM [x86_64-linux]
-e:1:in '': undefined method '~@' for an instance of Integer (NoMethodError)
Did you mean?  ~
```

After (matches parse.y):
```sh
$ ./miniruby -ve "puts 42.~@"
ruby 3.5.0dev (2025-10-16T03:40:45Z master https://github.com/ruby/prism/commit/1d95d75c3f) +PRISM [x86_64-linux]
-43
```

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

[ruby/prism] Make error and snapshot tests multi-version aware

2025-10-22T14:50:11+00:00

This one has been on my mind for a while now.

Currently, there are only tests against the latest syntax version.

This changes the snapshot structure as follows:
* Snapshots at their current location are tested against all syntax versions
* Snapshots inside a version folder like "3.3" are tested against all versions starting from that version
* Snapshots inside a version folder like "3.3-4.2" are tested against all versions in the given range.

This makes sure that as new syntax is added, older versions still work as expected.
I also added a few tests for now valid syntax that should be invalid in older versions (and the other way around as well)

These tests run really fast. So even though it does 3x the work for these, I am still able to run the whole test suite in just 11 seconds.

https://github.com/ruby/prism/commit/5191b1aa68