[Issue 16699] [REG 2.070] stack corruption with scope(exit)

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=16699

--- Comment #18 from hsteoh at quickfur.ath.cx ---
@Steven: I see your point about preventing redundant fixes. But it's still
confusing that a bug has been resolved as fixed, yet the bug persists in
master. :-)

Is there a way for bugzilla to indicate which branch(es) a bug has been fixed
in?  Debian's Bug Tracking System, for example, in the recent years got a new
feature where it keeps track of all the releases
(experimental/unstable/testing/stable) that a bug has been fixed in, so that
you can tell at a glance whether or not the fix is in the release you're
interested in.

Debian's BTS also tracks the package version number that a fix was first
implemented in, so you can check whether you have the fix by looking at the
version string, even if you're not using the official .deb repositories.
Although, this is probably not applicable in our case.

--