News for hackers. Stuff that matters.
Re:The Ergonomics of Type Checking (2016) by nearmuse on Saturday October 28, 2017 @03:24PM (#15576402)
So PEP 484? You can write out whatever and then add annotations (at least to the API).
Re:The Ergonomics of Type Checking (2016) by zero_iq on Saturday October 28, 2017 @04:35PM (#15576664)
Also Cython: start with pure Python and add types and other annotations to get the performance gains of static compilation (to C Python extension).
Re:The Ergonomics of Type Checking (2016) by pleasecalllater on Saturday October 28, 2017 @04:37PM (#15576672)
So you spend time writing the things, which then are totally ignored by the compiler/interpreter. Seems like a waste of time, except for documentation purpose.
Re:The Ergonomics of Type Checking (2016) by nearmuse on Saturday October 28, 2017 @06:21PM (#15576973)
Those are actually enforceable by IDE or interpreter/compiler if implemented. Even if this wasn't the case, it is better than some arbitrary variable naming convention or comments format.
Re:The Ergonomics of Type Checking (2016) by tedmiston on Saturday October 28, 2017 @06:39PM (#15577041)
You can check them at runtime with mypy.

http://mypy-lang.org/index.html

Re:The Ergonomics of Type Checking (2016) by dec0dedab0de on Saturday October 28, 2017 @05:09PM (#15576771)
Documentation is never a waste of time. Especially if your IDE is aware of it, and pointing out errors for you.