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

[via Digitalmars-d-bugs]

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

Steven Schveighoffer <schveiguy at yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |schveiguy at yahoo.com

--- Comment #21 from Steven Schveighoffer <schveiguy at yahoo.com> ---
(In reply to Ketmar Dark from comment #19)

> sure, this may add some burden on devs, but i believe that it is better and
> helthier way to do developement work.

Says the guy who thinks creating a github account is an undue burden ;)

In any case, the current workflow is not going to change, it works actually
quite well the way it is, and I would be very against changing it.

People file bug reports for released compilers not realizing it's already fixed
in master. They file duplicates all the time. We can't avoid all situations of
having someone miss that a bug is already fixed. What we can do, is avoid the
situation that a bug report is advertising a fix is needed, when one is already
implemented and accepted.

--