static type checking is like compile-time asserts -- it doesn't add to solution complexity, it just verifies assumptions about inherent existing complexity.
Yeah but typing related bugs which is what static type checkers catch only account for 3% of bugs.
You are always going to get more bang for buck by simply writing more unit tests.
Static typing is done primarily for performance and that requires a statically typed language. Hacking it into a scripting language is plain looking for trouble.
Seems like youve just abstracted things like static typing into a extension of the language thats checked at a less optimal time. At this point arent you better off just using a language that incorporates this functionality and compiles it? Sounds like youve just implemented static typing but in a really akward and unecessary way
reply