3 ms·
"Strong-typing vs weak-typing" is actually irrelevant. It's still an error at run-time, and unless your quality control tools and practices actually run the co
by qwer 13y ago
"Strong-typing vs weak-typing" is actually irrelevant. It's still an error at run-time, and unless your quality control tools and practices actually run the code (like unit tests do), you're not going to know about them.
As you move beyond native types, duck-typing (like in python) completely subverts the strong type-checks anyway.