nullability not enforced

[mrbkap]

Given the following program:

class Cat {
  public function meow() { print("meow"); }
}
function go(c : Cat!) {
  print("here");
  c.meow();
}
go(null);

I would expect the output to simply be the exception caused by passing null as a Cat!.

However, the current RI prints "here", indicating that the function call happened and the exception thrown in the example is thrown from the c.meow() line. I believe we should fail to convert null to a Cat! before entry into the function.

[jresig]

A simpler case (exception expected) - and escalating:

>> function test(foo: int!){ return foo; }
>> test(null);
0

[graydon]

There were several inter-related RI bugs in here, but they should mostly all be fixed in revision cbc9e83...

Though your second testcase is perhaps not so good; int is presently hard-wired into the scalar conversion table for backward compatibility with ES3 primitives. So null always converts to 0 when assigned to an int, nullable or otherwise. A better case follows:

class x {}
function test(v:x!) {}
test(null);