News for hackers. Stuff that matters.

A comment on Our journey to type checking 4M lines of Python. Parent comment

Re:Our journey to type checking 4M lines of Python by pilif on Sunday September 08, 2019 @04:04AM (#20909202)
> which will raise TypeError

At runtime. In production. A compiler would catch the problem at build time, never causing an error in production.

[ Parent | on HN ]
Re:Our journey to type checking 4M lines of Python by dbcurtis on Sunday September 08, 2019 @02:04PM (#20912182)
Maybe you missed this part:

> So of course you actually need to exercise the code also, which is where the hypothesis package comes in.

These are tests you should be doing anyway. Type checking does not excuse poor test coverage.

[ Parent | on HN ]
Re:Our journey to type checking 4M lines of Python by kalleboo on Sunday September 08, 2019 @09:17AM (#20910398)
> A compiler would catch the problem at build time

And a nice IDE/code editor would catch the problem as you're typing it

[ Parent | on HN ]
Re:Our journey to type checking 4M lines of Python by pilif on Sunday September 08, 2019 @09:23AM (#20910434)
Not in a dynamic language. Finding all possible inputs to your method that’s calling float() on its Arguments in a dynamic language is akin to solving the halting problem.

Also, error messages in an IDE can be ignored. Compiler errors can’t.

[ Parent | on HN ]