------- Comment #3 from  2009-01-26 08:33 -------
David - I agree with Brad. Sometimes the assertion in a precondition can be
quite complicated. I've occasionally inserted tests to check it.
(A precondition in a LIBRARY function is a test for USER code. Not a test for
the library code).

However, as I see it, asserts are basically a debugging feature. So they
shouldn't interfere with nothrow.

I wonder if assert could be made unrecoverable inside a nothrow function?
IE, compiles to d_assert_nothrow()
which tests the condition, and immediately quits if it is not met?

Since assert() is magical already.


Reply via email to