link: DevelopersMeeting20150820Japan - String literals are frozen (immutable) by default in Ruby 3.0https://docs.google.com/document/d/1e00tTj8ix2ofS8H2RiIMUhr39bABSc7AL0vk4KbtSF4/edit …
-
-
@wycats@yukihiro_matz It’s easy to fork a project and put some magic comments there. -
@a_matsuda@yukihiro_matz@evanphx if everyone forks every project and adds magic comments we're doing it wrong. -
@a_matsuda@yukihiro_matz@evanphx there are other plausible transition plans. -
@a_matsuda@yukihiro_matz@evanphx example: 2.3 warnings if a string literal is mutated. -
@wycats@a_matsuda@yukihiro_matz@evanphx This seems like a great idea to help set up for the transition. At least gives a heads up -
@sgrif@wycats@a_matsuda@yukihiro_matz@evanphx Ruby warnings though… I tried to run with them on and it’s untennable. -
@derekprior@wycats@a_matsuda@yukihiro_matz@evanphx We run with warnings in Rails. It's surprisingly easy if you commit to it. -
@sgrif@derekprior@wycats@yukihiro_matz@evanphx True. Only when you're not bundling sass :trollface: - 3 more replies
New conversation -
-
-
@yukihiro_matz and a gem returning an immutable string may be fine in isolation, but when passed to another gem,
-
@yukihiro_matz in other words, gems don't say "I take a mutable string", they say "I take a string", so the problems will be subtle. -
@wycats@yukihiro_matz This shows that it’s not that a hard work to upgrade existing libraries. -
@a_matsuda@yukihiro_matz it's not always trivial to understand interactions between many libs. -
@wycats@a_matsuda@yukihiro_matz See also: NPM. :trollface: - End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.