https://issues.dlang.org/show_bug.cgi?id=9279
--- Comment #8 from Vladimir Panteleev <[email protected]> --- (In reply to Kenji Hara from comment #7) > I'm not sure it should be called "regression". Yes, the two enhancement PRs > appended the cases of original wrong-code bug, caused by the undetection of > escaping reference to local data. However the bug exists from the very old > versions... Is this about semantics? IMO a regression is the effect of a change, not the nature of the change itself (i.e. whether it introduces a bug or merely exposes a latent bug). You can call it whatever you like, but ultimately the effect is that something works as expected in version N and then doesn't in version N+1. If we were to all sit down, discuss, and agree to use different terminology for different kinds of causes and effects, I could start calling them something else, though I think that would be a terrible waste of time. Anyway, I hope my regression notifications on the pull requests aren't too demotivating. I don't know how I would feel if I received so many regression notifications. I certainly don't intend to accuse anyone of anything - I would like to know if a change that I authored or reviewed introduced a regression, which is why I'm posting the GitHub comments. --
