Re: assert(0) behavior

[Steven Schveighoffer via Digitalmars-d]

On 8/4/15 4:43 PM, Steven Schveighoffer wrote:
I should say, any assert(0) with a message printed that is possible to
trigger in release mode is an error. If you can ensure it's only
possible to trigger when compiled in debug mode (or for unit tests),
then assert(0, msg) is fine.

In that vein, would it be possible to make this a warning? i.e. if you 
compile a file in -release mode, and the compiler encounters an 
assert(0, msg), it emits a warning?

-Steve