Skip to content
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

Use version: 3.3.1 against Translation::Parser #2771

Merged
merged 1 commit into from
May 4, 2024

Conversation

koic
Copy link
Contributor

@koic koic commented May 4, 2024

Follow up #2760.

This PR updates the Translation::Parser to use version 3.3.1 when the version 3.3 is specified. The Parser gem is structured to support the latest patch versions, hence this aligns with Parser-compatible versioning. As noted in #2760, the behavior remains unchanged with this switch from 3.3.0 to 3.3.1.

@koic koic force-pushed the use_3_3_3_against_translation_parser branch from 52ef5cf to 20c1903 Compare May 4, 2024 05:03
Follow up ruby#2760.

This PR updates the `Translation::Parser` to use version 3.3.1 when the version 3.3 is specified.
The Parser gem is structured to support the latest patch versions, hence this aligns with Parser-compatible versioning.
As noted in ruby#2760, the behavior remains unchanged with this switch from 3.3.0 to 3.3.1.
@koic koic force-pushed the use_3_3_3_against_translation_parser branch from 20c1903 to efde09d Compare May 4, 2024 05:59
@kddnewton kddnewton merged commit e418265 into ruby:main May 4, 2024
54 checks passed
@koic koic deleted the use_3_3_3_against_translation_parser branch May 4, 2024 16:46
ParadoxV5 added a commit to ParadoxV5/prism that referenced this pull request May 25, 2024
As observed in ruby#2771, `?=` thinks that implicit definitions of CC`, `AR` and `ARFLAGS` are explicit.
Disabling implicit variables is more straightforward than adapting the `Makefile` and `extconf.rb` around them.
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