Re:Strong Types and Their Impact on Testing
by kod on Wednesday November 19, 2014 @01:26PM
(#8631661)
No, a compile time error is nothing at all like a runtime null pointer exception.
Given that the language supports subtype polymorphism, this is exactly how the type inference should work. Any is the narrowest available supertype.
If you don't like it, there's a pretty simple fix: add an explicit type ascription, which you should be doing for the return values of any methods anyway.
Re:Strong Types and Their Impact on Testing
by dllthomas on Wednesday November 19, 2014 @06:17PM
(#8633344)
It's like a null reference in that both increase the distance between the error and the report of failure, and both have a way of working correctly.
The distinction between compile time failure and runtime failure is an important one, but not the only thing going on.
There have been attempts to fix this - WartRemover specifically has a Wart for any uses of Any for example.