checkedint call removal

[via Digitalmars-d]

On Friday, 1 August 2014 at 02:46:48 UTC, Walter Bright wrote:
> On 7/31/2014 1:36 PM, Tofu Ninja wrote:
>> On Thursday, 31 July 2014 at 19:12:04 UTC, Walter Bright wrote:
>>> Integers are sortable, period. That is not "input".
>>
>> Ok so sorted ints are not "input", what else is not "input"? 
>> Where can I draw
>> the line? And if I do use assert on an input, that is what? 
>> Undefined? I thought
>> D was not supposed to have undefined behavior.
>
> I've answered this so many times now, I no longer have any new 
> words to say on the topic.

I'll say some word on this, then.

Yes, you cannot assert() that input has a specific value. 
Programs that do this are provable not correct.

You can assert() that input has a specific value after the code 
has made sure that it has a specific value. This means the 
program is partially correct.

Input is a priori assumed to have any value allowed by the 
context.
Argc has an implicit assume that provides axioms describing the 
limits of int/C/unix/etc.