ruby.git/test/prism/errors_test.rb, branch v4.0.3

[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] Add tests to `regexp_encoding_option_mismatch`

2025-11-20T20:09:19+00:00

related to #2667

https://github.com/ruby/prism/commit/44f075bae4

[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

[ruby/prism] [Bug #17398] Allow `private def hello = puts "Hello"`

2025-09-12T19:00:01+00:00

This was a limitation of parse.y that prism intentionally replicated.

https://github.com/ruby/prism/commit/8fd12d594c

[ruby/prism] No writing to numbered parameters

2025-02-13T20:04:02+00:00

Fixes [Bug #21117]

https://github.com/ruby/prism/commit/19d4bab5a0

[ruby/prism] Blocks & kwargs are not valid in index assignments

2024-12-16T15:00:27+00:00

Ruby feature: https://bugs.ruby-lang.org/issues/20952

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

[ruby/prism] Fix error messages for unterminated ( and {

2024-12-05T18:42:01+00:00

If we hit an EOF token, and the character before the EOF is a newline,
we should make EOF token start at the previous newline.  That way any
errors reported will occur on that line.

For example "foo(\n" should report an error on line 1 even though the
EOF technically occurs on line 2.

[Bug #20918]
https://bugs.ruby-lang.org/issues/20918

https://github.com/ruby/prism/commit/60bc43de8e

[ruby/prism] Sync from ruby/ruby

2024-07-25T18:59:10+00:00

https://github.com/ruby/prism/commit/280517c325

[ruby/prism] Various cleanup for initializers and typechecks

2024-07-11T18:25:54+00:00

https://github.com/ruby/prism/commit/86cf82794a

[ruby/prism] Reconfigure error tests

2024-07-11T18:25:54+00:00

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