You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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.
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!
The text was updated successfully, but these errors were encountered: