assume, assert, enforce, @safe

[Ary Borenszweig via Digitalmars-d]

On 8/1/14, 2:19 PM, Sebastiaan Koppe wrote:
> If assertions are disabled in release builds, and you specifically
> instruct the compiler to build one, are you not assuming that the
> assertions will hold?
>
> Then what is wrong with extending those assumptions to the optimizer?
>
> Unless the assertions trigger in debug build, you will not end up with
> bugs in the release.

If assertions don't trigger in debug build then assertions don't trigger 
in release.

That's false.