Skip to content

Conversation

@kddnewton
Copy link
Collaborator

No description provided.

@kddnewton kddnewton merged commit a08cde8 into main Dec 21, 2024
54 of 56 checks passed
@kddnewton kddnewton deleted the support-3-5-version branch December 21, 2024 20:35
@eregon
Copy link
Member

eregon commented Dec 23, 2024

@kddnewton Currently there are bunch of versions comparisons like

prism/src/prism.c

Line 2969 in 3c4851c

if (parser->version != PM_OPTIONS_VERSION_CRUBY_3_3) {
in prism.c
I think they are correct because all conditions use PM_OPTIONS_VERSION_CRUBY_3_3 (and it is the lowest version) and none use 3_4/LATEST (which would most likely result in a bug) but it feels brittle.
WDYT about giving enum values that increase with newer versions? (e.g. 3.3 = 33, 3.4 = 34, latest = 99)
That way one could do e.g. parser->version >= PM_OPTIONS_VERSION_CRUBY_3_4 instead of parser->version != PM_OPTIONS_VERSION_CRUBY_3_3, which seems a lot clearer about intent (behavior for 3.4+).

koic added a commit to koic/prism that referenced this pull request Dec 25, 2024
Follow up ruby#3336.

Development for Ruby 3.5 has begun on the master branch:
ruby/ruby@2f064b3
matzbot pushed a commit to ruby/ruby that referenced this pull request Dec 26, 2024
Follow up ruby/prism#3336.

Development for Ruby 3.5 has begun on the master branch:
2f064b3

ruby/prism@aa49c1bd78
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.

3 participants