On Thu, 2010-07-15 at 15:00 -0700, Walter Bright wrote: > > Andrei Alexandrescu wrote: > > > > 4. DESIRED: assert is NOT hacked, any failing assert ends the current > > unittest, the failure message is printed, execution continues with the > > next unittest, program ends with error code if at least one assert > > failed, everybody's happy. > > > > Everybody's happy except the guys like me who want to run all the unit > tests in one go.
But that is trivial to implement as a library feature! The biggest problem, as I see it, is that assert(), which is a *built-in* feature of the language, now has radically different semantics depending on where and when it is called. Besides, the behaviour Andrei and the rest of us want can't be implemented in a library. -Lars _______________________________________________ phobos mailing list [email protected] http://lists.puremagic.com/mailman/listinfo/phobos
