checkedint call removal

[Daniel Gibson via Digitalmars-d]

Am 02.08.2014 22:02, schrieb Johannes Pfau:
> Am Sat, 02 Aug 2014 12:19:41 -0700
> schrieb Walter Bright <newshound2 at digitalmars.com>:
>
>> On 8/2/2014 6:20 AM, Artur Skawina via Digitalmars-d wrote:
>>> The bug was _introduced_ by the assert, the code was 100% correct.
>>
>> Asserts are part of the code, and writing incorrect asserts is
>> writing buggy code.
>>
>
> Just some meta points:
>
> I just want to point out that nobody wants to hear 'your code was buggy
> anyway' after a compiler update broke working code. A few months ago
> you and Andrei were talking about PR and you often said that D is now
> 'stable' and 'ready for production'. But we still hear claims on reddit
> and other sites that D is unstable, breaks code with every release, etc.
>
> And you still think that changing the behavior of assert is a good
> idea? Even if assert was always meant to work like this, even if the
> spec clearly defined it this will be a PR disaster. People don't care
> what was in the spec, the only thing they know is the code worked

And it's not even in the spec, at least not explicitly (maybe it's now, 
but it hasn't been a few  days ago).

Cheers
Daniel