@sgrif @wycats @a_matsuda @yukihiro_matz @evanphx Ruby warnings though… I tried to run with them on and it’s untennable.
-
-
Replying to @derekprior
@derekprior@wycats@a_matsuda@yukihiro_matz@evanphx We run with warnings in Rails. It's surprisingly easy if you commit to it.2 replies 0 retweets 0 likes -
Replying to @sgrif
@sgrif@derekprior@wycats@yukihiro_matz@evanphx True. Only when you're not bundling sass :trollface:1 reply 0 retweets 0 likes -
Replying to @a_matsuda
@a_matsuda@sgrif@derekprior@yukihiro_matz@evanphx I would argue that it should be an on-by-default warning before it's an error.1 reply 0 retweets 0 likes -
Replying to @wycats
@a_matsuda@sgrif@derekprior@yukihiro_matz@evanphx So maybe 2.3 it's a warning (--warn-frozen-strings), 2.4 it's an on-by-default warning2 replies 1 retweet 2 likes -
Replying to @wycats
@wycats@a_matsuda@sgrif@derekprior@yukihiro_matz —error-frozen-strings would be good too, that will let people try out 3.0 behavior1 reply 0 retweets 1 like -
Replying to @evanphx
@evanphx@a_matsuda@sgrif@derekprior@yukihiro_matz Yeah, absolutely, especially if it comes with allocation traces.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@a_matsuda@sgrif@derekprior@yukihiro_matz In fact, having that in 2.3 could let people try it. If it works ok, could be on in 3.01 reply 0 retweets 0 likes -
Replying to @evanphx
@evanphx@a_matsuda@sgrif@derekprior@yukihiro_matz right exactly. I don't know if it's a big issue, but let's find out!1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@a_matsuda@sgrif@derekprior@yukihiro_matz Exactly. Use science to figure out it's effects.1 reply 0 retweets 0 likes
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.