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

[via Digitalmars-d-bugs]

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

--- Comment #23 from Steven Schveighoffer <schveiguy at yahoo.com> ---
(In reply to Ketmar Dark from comment #22)
> (In reply to Steven Schveighoffer from comment #21)
> > People file bug reports for released compilers not realizing it's already
> > fixed in master.
> 
> how can it be? if there was bug, and it was fixed -- we have closed
> bugreport.

It's simple. Person downloads latest compiler release, tries something, doesn't
work. They file a bug.

People don't regularly use the master release of the compiler. Yes, we have a
very very good system for making sure that the master compiler is generally
usable, but it means building from scratch. Most people just want to get work
done, and are not interested in compiler/runtime development.

In any case, I think the system works just fine as is. Just close a bug when
its commit is in master or stable, and we should be fine.

If we had a "FIXED IN STABLE" bugzilla resolution, that was then moved to just
"FIXED" automatically when the merge occurred, then perhaps this would be
helpful. But I don't think it's necessary. The amount of time between a bug
being fixed in stable and then moving to master is quite small. Seems like a
lot of effort for such little gain.

--