3 ms·
The type checking isn't lax at all, at least not in Python.
by mkesper 12y ago
The type checking isn't lax at all, at least not in Python.
- ufo 12y agoThe problem in Python is that type errors end up being reported later than they would in a typed language. For example, if I have a function f that expects an object and call it with f(None) its not going to immediately give me an error. Its only going to give an error when I try to call a method on that `None` and depending on how my program is structured the line with the erroneous f(None) call might not even end up appearing in the final stack trace.