@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
@yukihiro_matz and a gem returning an immutable string may be fine in isolation, but when passed to another gem,
3 replies 0 retweets 1 like -
Replying to @wycats
@wycats@yukihiro_matz
this makes sense. Good point :(1 reply 0 retweets 0 likes -
Replying to @searls
@searls@wycats@yukihiro_matz Users will add the comment to every file because that will be the fastest way to fix their problem.1 reply 0 retweets 0 likes -
Replying to @evanphx
@evanphx@searls@yukihiro_matz they won't necessarily be able to fork every gem and add the comment.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@evanphx@searls@yukihiro_matz Growing up is hard.2 replies 1 retweet 3 likes
@headius @evanphx @searls @yukihiro_matz come on man. I'm talking about how to make the transition better and you give me this?
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.