While I regularly complain about unexpected/undocumented change, I think Alon's plan is pretty careful and reasonable.
Badly named variables are a perpetual mental hassle, and triggering a clear error message means the change won't be obscure. Cheers! Beuc On 17/10/2019 17:02, Gabriel Cuvillier wrote: > > 100% agree with Floh there. Changing such a thing is an open door > to a very obscure, hard to find, and unwanted potential "project > breaker", for a very minor added value... > > Having to live with some minor technical debt due to badly named > things is acceptable I suppose. > > > Le 17/10/2019 à 16:51, Floh a écrit : > >> Isn't there at lot code out there in the wild that would be >> broken by >> such as change? >> >> Yeah. TBH I'm not a fan of a name change even if the new name is >> slightly more fitting. That's one of those obscure things that >> suddenly breaks projects, usually at the worst possible time (even >> with a deprecation note and period, this stuff is usually ignored). >> If such a change would come with a real benefit (such as better >> performance, or less code maintenance in the future) I'd be all for >> it, but not when it's just one of the many "badly named things" in >> computing :) -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/10c8a820-5a3a-d1a6-dec2-6694dd9631ea%40beuc.net.
