Skip to content

Warning parser when Ruby3.4.3 #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
akichim21 opened this issue Apr 21, 2025 · 6 comments
Closed

Warning parser when Ruby3.4.3 #16

akichim21 opened this issue Apr 21, 2025 · 6 comments

Comments

@akichim21
Copy link

Probably because proc_to_ast depends on the parser, I get warnings in Ruby 3.4.

warning: parser/current is loading parser/ruby34, which recognizes 3.4.0-dev-compliant syntax, but you are running 3.4.3.
Please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.

whitequark/parser#1065

@sue445
Copy link
Contributor

sue445 commented Apr 21, 2025

This is parser gem's problem, not proc_to_ast and rspec-parameterized

@sue445 sue445 closed this as completed Apr 21, 2025
@akichim21
Copy link
Author

@sue445
Hi.
The parser gem seems to have a policy of not supporting 3.4 or later in the future.
It seems that it is necessary to migrate to Prism.
whitequark/parser#1056 (comment)
whitequark/parser#1046

Or there may be a response to prevent warnings like i18n-task.
https://github.com/glebm/i18n-tasks/pull/613/files

@sue445
Copy link
Contributor

sue445 commented Apr 22, 2025

@akichim21 I see

However, issue of parser gem warnings and prism support should be treated as separate issues, so I created a separate issue.

#17

@akichim21
Copy link
Author

Thanks!

@sue445
Copy link
Contributor

sue445 commented May 2, 2025

@akichim21 rspec-parameterized-core v2.0.0 supports both Parser gem and Prism gem

c.f. https://github.com/rspec-parameterized/rspec-parameterized-core/blob/main/CHANGELOG.md#200---2025-05-02

@akichim21
Copy link
Author

Great job!
Thank you for your response.
I have confirmed that there are no warnings when running the rspec.

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

No branches or pull requests

2 participants