@wycats No, you just need magic comment for mutable string literals after Ruby3.0.
-
-
Replying to @yukihiro_matz
@yukihiro_matz This could become like Python 3. It can break gems that mutate strings (gsub! even) and will be hard to track down.3 replies 1 retweet 2 likes -
-
Replying to @wycats
@yukihiro_matz most programs have dozens or hundreds of third party dependencies.2 replies 0 retweets 1 like -
Replying to @wycats
@wycats@yukihiro_matz It’s easy to fork a project and put some magic comments there.3 replies 0 retweets 0 likes -
Replying to @a_matsuda
@a_matsuda@yukihiro_matz@evanphx if everyone forks every project and adds magic comments we're doing it wrong.1 reply 0 retweets 5 likes -
Replying to @wycats
@a_matsuda@yukihiro_matz@evanphx there are other plausible transition plans.1 reply 0 retweets 0 likes -
Replying to @wycats
@a_matsuda@yukihiro_matz@evanphx example: 2.3 warnings if a string literal is mutated.2 replies 0 retweets 1 like -
Replying to @wycats
@wycats@a_matsuda@yukihiro_matz@evanphx This seems like a great idea to help set up for the transition. At least gives a heads up2 replies 0 retweets 0 likes
@sgrif @a_matsuda @yukihiro_matz @evanphx perhaps a debug mode would even store the source location of the string.
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.