Diminishing returns of static typing

Re:Diminishing returns of static typing by nightski on Monday October 02, 2017 @02:41PM (#15386604)

I haven't used optional typing in python. However, the problem I see with optional typing is that while I may choose to use it my team mates might not. Even more importantly, the 3rd party dependencies I use probably don't. So the amount of code that actually uses the types would be very limiting. Saying the choice is entirely up to you personally is a misnomer.

[ Parent | on HN ]

Re:Diminishing returns of static typing by gipp on Monday October 02, 2017 @03:07PM (#15386884)

Strict use of type annotations has to be a team decision, yes. Checking for them can be integrated into a CI build, though.

The typing spec provides for supplementary "stub files" that can be provided for third-party dependencies without their own annotations. The typeshed project provides these for a fair and quickly increasing number of common dependencies, and is plugged into pycharm and mypy by default: https://github.com/python/typeshed

[ Parent | on HN ]

Re:Diminishing returns of static typing by yawaramin on Monday October 02, 2017 @03:43PM (#15387259)

I think GP meant 'you' as in 'your team'. Anyway, Python has a type repository for popular libraries, just like TypeScript does. And mypy can still typecheck your code even without type annotations.

[ Parent | on HN ]