An error (with a line number) would be even better than an assert in many cases, as it would at least give an indication of what need to be changed to work around the compiler bug.
On Fri, Mar 30, 2012 at 21:58, Don Clugston <[email protected]> wrote: >> On 29.03.2012 22:54, Walter Bright wrote: >>> >>> But first we have several new regressions to deal with: >>> >>> http://d.puremagic.com/issues/buglist.cgi?query_format=advanced&bug_severity=regression&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED > > I think we should also introduce of policy of never shipping with > known compiler segfaults. The relevant bugs don't necessarily need to > be fixed, just replaced > with an assert, so it's hardly any work. There's only a couple of them > right now. > Likewise bug 7190 -- it's a simple infinite loop, that doesn't even > cause a stack overflow, so DMD just hangs. It should become an assert > failure. > _______________________________________________ > dmd-beta mailing list > [email protected] > http://lists.puremagic.com/mailman/listinfo/dmd-beta _______________________________________________ dmd-beta mailing list [email protected] http://lists.puremagic.com/mailman/listinfo/dmd-beta
