What I get from this : if performance and speed is not an issue, Python is good. But, if you want speed, use something else (C, C++…).
Compiling typed Python: types are very broad hints and they are sometimes lies.
Submitted 1 year ago by abobla@lemm.ee to programming@programming.dev
https://bernsteinbear.com/blog/typed-python/
Comments
A_A@lemmy.world 1 year ago
Moc@lemmy.world 1 year ago
Python and Rust apparently pair nicely
UlrikHD@programming.dev 1 year ago
Could you elaborate on that point? Is it as smooth as using C?
lysdexic@programming.dev 1 year ago
This was the first time I saw someone refer to Python’s type hints as a performance tool. Up until now, I only saw references to type hints as a way to help static code analyzer tools verify that objects and invocations comply with contracts.
I guess that having additional info at hand to determine how some calls are expected to be made is helpful to gather info to drive optimization steps, but PEP 484 is clear in stating that it’s goal is to help type checkers, and that code generation using type hints might be limited to some contexts.
This sounds like yet another example supporting the old law of interfaces, where all it takes for an interface to be abused is for it to exist.