News for hackers. Stuff that matters.

A comment on Adoption of Mypy for Python type checking: 45% already use it, 40% don't plan to. Parent comment

Re:Adoption of Mypy for Python type checking: 45% already us... by you_are_naive on Sunday March 21, 2021 @11:02AM (#26530961)
The biggest problem with mypy is that it's written in python. It's slow. It needs to be rewritten in rust or go to make it faster like how js ecosystem is moving in that direction. All the tooling is moved to faster compiled languages.
[ Parent | on HN ]
Re:Adoption of Mypy for Python type checking: 45% already us... by watermelon0 on Sunday March 21, 2021 @11:29AM (#26531156)
mypy is actually compiled via mypyc, which should be a few times faster than interpreted Python https://github.com/python/mypy/tree/master/mypyc
[ Parent | on HN ]
Re:Adoption of Mypy for Python type checking: 45% already us... by crazypython on Sunday March 21, 2021 @11:06AM (#26530987)
mypy has implementations in other languages – PyCharm's is in Java, Facebook's Pyre's is in OCaML https://github.com/facebook/pyre-check
[ Parent | on HN ]
Re:Adoption of Mypy for Python type checking: 45% already us... by MapleWalnut on Sunday March 21, 2021 @11:52AM (#26531306)
Those tools are not re-implementations of mypy, but their own type checkers. Pyre doesn't necessarily have all the features of mypy and vice versa.
[ Parent | on HN ]
Re:Adoption of Mypy for Python type checking: 45% already us... by wk_end on Sunday March 21, 2021 @02:17PM (#26532545)
Initial type checking with mypy is slow, but if you use mypy-daemon each check after that becomes pretty much instantaneous, even on 10M+ line code bases.
[ Parent | on HN ]