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

support ruby 2.4 frozen string literals #118

Closed
flavorjones opened this issue Feb 13, 2017 · 4 comments
Closed

support ruby 2.4 frozen string literals #118

flavorjones opened this issue Feb 13, 2017 · 4 comments
Milestone

Comments

@flavorjones
Copy link
Owner

as of 7a10151, there are 605 errors when running tests with RUBYOPT="--enable-frozen-string-literal --debug=frozen-string-literal"

Acceptance criteria:

  • ruby 2.4 test task runs with frozen-string-literal ruby options set and passes
@flavorjones
Copy link
Owner Author

Loofah tests now pass; remaining failures need support from Crass. Will open a PR to that project.

@flavorjones
Copy link
Owner Author

See rgrove/crass#3 to monitor progress. Closing this ticket.

@flavorjones
Copy link
Owner Author

Actually, reopening so that once Crass supports this option, I can bake it into Loofah's tests.

@flavorjones flavorjones reopened this Nov 13, 2017
@flavorjones
Copy link
Owner Author

OK - revisiting this, all tests pass locally when run with RUBYOPT="--enable-frozen-string-literal --debug=frozen-string-literal" so now I want to add this to the CI pipelines.

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

1 participant