assert semantic change proposal

[via Digitalmars-d]

On Wednesday, 6 August 2014 at 06:56:40 UTC, eles wrote:
> I feel that, at this stage, is only about how a compiler glag, 
> specifically "-release" works. For other configurations, there 
> is no problem: event if the optimizer optimizes based on 
> asserts, the asserts themselves are part of the code: code is 
> there and the assertion will fail before execution enters the 
> optimized path. This is just like any other optimization, 
> nothing special about it.

Not right:

b = a+1
assume(b>C)

implies

assume(a+1>C)
b = a+1