Open-sourcing MonkeyType – Let your Python code type-hint itself

Re:Open-sourcing MonkeyType – Let your Python code type-hint... by Barrin92 on Friday December 22, 2017 @03:40PM (#15990720)

you'll have to expand on this a little for me. I just recently looked at an older Haskell codebase I was working on two years ago, and simply because of a very few straight forward types, nothing special, I could really wrap my head around the code-base a lot easier. Not just because the code tells me in plain text what types occur where, but also because enforcing a strong type system encouraged compositionality and well-formed behaviour in the first place.

If I look at some of the python code I've written, I'll be perfectly honest I often cannot tell you what to make of it any more.

[ Parent | on HN ]

Re:Open-sourcing MonkeyType – Let your Python code type-hint... by dmitriid on Friday December 22, 2017 @05:56PM (#15991599)

Types being code depend on people writing them (as is the rest of the code :) ). I guess you’re lucky/smart that your code base is just simple types.

Quite often people construct complex type hierarchies just because they can (or don’t know better). And it’s a pain to wade through and coerce to what you want it to do.

I’m very much on the fence between static and dynamic typing, having used (and probably abused) both. I prefer a “pragmatically” typed language, but I haven’t come up with a proper definition for it yet :)

[ Parent | on HN ]