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

Immutable/Frozen String Compatibility #311

Open
kenpropel opened this issue Jun 30, 2017 · 3 comments
Open

Immutable/Frozen String Compatibility #311

kenpropel opened this issue Jun 30, 2017 · 3 comments

Comments

@kenpropel
Copy link

Is Ruby's (potentially) upcoming Frozen String Literal compatibility in the roadmap?

Runtime option --enable-frozen-string-literal has been available since Ruby 2.3 and using this gives me RuntimeErrors with em-http v.1.1.5 so I'm curious what the take is with this project.

Thanks!

@igrigorik
Copy link
Owner

Is there a tl;dr on the motivation and impact of this change in core? Not sure I fully grok either.

That said, happy to take/review PR's, if anyone is willing.. :-)

@kenpropel
Copy link
Author

Thanks for replying.

https://twitter.com/yukihiro_matz/status/634386185507311616
This is the most official it gets that I can find from Matz. But tl;dr it's for Ruby performance. Since it won't become default until 3.0 (which doesn't have a release date yet) there's no rush.

I was just curious because I started experimenting this frozen string option. I'll keep playing with some of my projects and see how this goes, or how soon the communities move towards this direction.

@igrigorik
Copy link
Owner

Interesting, thanks for the heads up. As you can tell, not something on my radar.. but if anyone is interested in making a PR, I'd be happy to review.

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