@wycats it's off by default. compatibility comes first.
-
-
@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: -
@a_matsuda@sgrif@derekprior@yukihiro_matz@evanphx I would argue that it should be an on-by-default warning before it's an error. -
@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 warning - End of conversation
New conversation -
-
-
@wycats@a_matsuda@yukihiro_matz@evanphx gotta say, Twitter is the worst possible way to offer feedback on major changes like this -
@qrush@a_matsuda@yukihiro_matz@evanphx Probably a worse way is to not offer feedback at all.
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.