Skip to content

Conversation

@Earlopain
Copy link
Collaborator

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

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

Otherwise, it uses the latest prism version
@Earlopain Earlopain force-pushed the unskip-tests branch 6 times, most recently from b66c79c to 729a02d Compare December 2, 2025 11:56
@Earlopain
Copy link
Collaborator Author

The first commit fixes an issue where the ripper translator parses code with the latest version instead of the currently running version. Found while cleaning up the excludes.

Also openend https://bugs.ruby-lang.org/issues/21756. The rest are as far as I can tell something that should be changed in prism.

@Earlopain Earlopain marked this pull request as ready for review December 2, 2025 12:03
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
@kddnewton kddnewton merged commit 0a3690f into ruby:main Dec 2, 2025
64 checks passed
@Earlopain Earlopain deleted the unskip-tests branch December 3, 2025 07:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants