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.
- Re: assume, assert, enforce, @safe Walter Bright via Digitalmars-d
- Re: assume, assert, enforce, @safe Tofu Ninja via Digitalmars-d
- Re: assume, assert, enforce, @safe Timon Gehr via Digitalmars-d
- Re: assume, assert, enforce, @safe Timon Gehr via Digitalmars-d
- Re: assume, assert, enforce, @safe David Bregman via Digitalmars-d
- Re: assume, assert, enforce, @safe Andrei Alexandrescu via Digitalmars-d
- Re: assume, assert, enforce, @safe Daniel Gibson via Digitalmars-d
- Re: assume, assert, enforce, @safe Daniel Murphy via Digitalmars-d
- Re: assume, assert, enforce, @safe Daniel Gibson via Digitalmars-d
- Re: assume, assert, enforce, @safe H. S. Teoh via Digitalmars-d
- Re: assume, assert, enforce, @safe Sebastiaan Koppe via Digitalmars-d
- Re: assume, assert, enforce, @safe Ary Borenszweig via Digitalmars-d
- Re: assume, assert, enforce, @safe Timon Gehr via Digitalmars-d
- Re: assume, assert, enforce, @safe eles via Digitalmars-d
- Re: assume, assert, enforce, @safe Tofu Ninja via Digitalmars-d
- Re: assume, assert, enforce, @safe eles via Digitalmars-d
- Re: assume, assert, enforce, @safe Timon Gehr via Digitalmars-d
- Re: assume, assert, enforce, @safe eles via Digitalmars-d
- Re: assume, assert, enforce, @safe Timon Gehr via Digitalmars-d
- Re: assume, assert, enforce, @safe Daniel Gibson via Digitalmars-d
- Re: assume, assert, enforce, @safe Jonathan M Davis via Digitalmars-d