On 3/12/2014 6:30 PM, Kapps wrote:
I used to get frustrated when my code would randomly break every compiler update
(and it shows how much D has progressed that regressions in my own code are now
a rare occurrence), but unexpected regressions such as the std.json regression
are much different from intended changes with plenty of time and warning that
provide an overall (even if slight in many cases) benefit to the end-user.
I got caught by breaking changes myself. I even approved the changes. But they
unexpectedly broke projects of mine, and I had to go through updating & fixing
them, supplying updates, etc.
It sux.
And it's much, much, much worse if you've got lots of legacy code with only a
vague idea of how it works because the engineers who wrote it have moved on, etc.
