5 Aug
2009
5 Aug
'09
4:25 p.m.
On 8/5/09 5:33 PM, Alessio Stalla wrote: […]
Also, I have a question about your patch: do you have a specific reason to handle null by always signaling an error? In principle, null is assignable to any non-primitive type, so the type error ought to be signaled only for primitive types, imho.
No good reason: I was just trying to refactor the logic, but misunderstood your intent (that "null is assignable to any non-primitive type") so it is incorrect as it stands.
--
"A screaming comes across the sky. It has happened before, but there
is nothing to compare to it now."