On Tuesday, September 15, 2015 at 11:11:52 AM UTC-5, Edward K. Ream wrote:
TL;DR: I am unlikely to be interested enough in type checking for Python. > I'm looking for a problem that a) seems impossible and b) hasn't been significantly studied. [big snip] > Over the last few years I have tried in vain to understand how various type-checking/inference algorithms have worked...It seems that I need better tools to understand the code. I doubt that better tools can take the place of understanding relevant theory ;-) My interest in Python's type hints is waning rapidly. Progress on the project is well along, and certainly does not need my "help". For instance, I understand none of the related type hinting issues <https://github.com/ambv/typehinting/issues>. Happily, Guide is on top of things :-) Perhaps more importantly, type hinting/checking could be a mixed blessing, as discussed here <https://github.com/ambv/typehinting/issues>. And a troubling type loophole <https://github.com/ambv/typehinting/blob/master/VARIANCE.rst> casts further doubts on the project. In short, I'm probably not qualified to contribute anything to the pep 484 <https://www.python.org/dev/peps/pep-0484/> project, and even if the project succeeds, it will add nothing to Leo. So looking elsewhere for a "big" project seems appropriate. Edward P.S. Having said all this, I *am* curious about how various type-related problems will be solved, so it's possible I'll start a conversation with the lead devs. EKR -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
