On 11/11/2016 08:30 AM, Dicebot wrote:
On Friday, 11 November 2016 at 13:21:40 UTC, Nick Sabalausky wrote:
Run the new dmd. If it fails, either fix your code or go temporarily
go back to the old dmd until you can fix your code.
D will never be considered production ready as pong as this attiude
remaind. Your described scenario in practice works like this:
- You decide to delay fix until you have time to investigate
I've gone through a lot of compiler upgrades on a lot of D projects, and
in my experience, this "investigate and fix for the new dmd" has always
been trivial (aside from one instance where Phobos's standard function
deprecation policy wasn't followed).
Some things should certainly have a smooth transition path (like above,
when replacing a Phobos function with a different one), but really, not
everything needs to be.
- Half of users of your library you (or your colleagues) complain that
they can't upgrade their projects because you areso slow
- You desperately find time to do required fix which proves bavkwards
incompatible
AFAICT, That's not the case with this particular cycle detection matter.
