Skip to content

support Ruby 2.4's frozen string literals (on master) #81

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

Merged

Conversation

flavorjones
Copy link
Collaborator

Note this change is made relative to master.

To test before/after, set RUBYOPT="--enable-frozen-string-literal --debug=frozen-string-literal"

@flavorjones flavorjones changed the title support Ruby 2.4's frozen string literals support Ruby 2.4's frozen string literals (on master) Feb 16, 2017
@zenspider
Copy link
Member

This looks fine to me... CI failure is not related as best I can tell... I would feel better if the CI were configured to include 2.4.

@alexdowad
Copy link
Contributor

Looks fine to me.

Note this change is made relative to master.
@flavorjones flavorjones force-pushed the flavorjones-master-frozen-string-literal branch from bc3aa11 to 830ba4a Compare November 22, 2017 04:04
for ruby 2.4 and higher, to prevent regressing on frozen literal support.
@flavorjones flavorjones force-pushed the flavorjones-master-frozen-string-literal branch from 830ba4a to 3f8e7f3 Compare November 22, 2017 04:31
@flavorjones
Copy link
Collaborator Author

Merging onto master.

@flavorjones flavorjones merged commit c92678b into ruby:master Nov 22, 2017
@flavorjones flavorjones deleted the flavorjones-master-frozen-string-literal branch November 22, 2017 04:35
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.

5 participants