assume, assert, enforce, @safe

[Kagamin via Digitalmars-d]

On Thursday, 31 July 2014 at 21:29:59 UTC, Sean Kelly wrote:
> So effectively, any factor occurring at runtime.  If I create a
> library, it is acceptable to validate function parameters using
> assert() because the user of that library knows what the library
> expects and should write their code accordingly.  That's fair.

He should, but what if he doesn't and the library is phobos or 
druntime (which are compiled in release mode)? BTW, druntime 
can't use enforce and doesn't verify its input.