Much of the Python codebase has type hinting in the comments (for example in [auto_scheduler code](https://github.com/apache/tvm/blob/main/python/tvm/auto_scheduler/compute_dag.py)). In theory adding type hinting in function arguments could be automated in this case.
For Python code that does not have that, what kind of transition plan would make sense? Notifying authors of functions from `git blame`, and giving them some months to make a new PR? Or perhaps making it a community effort to transition? It could be a good way to onboard new and early stage contributors, since a) the required code changes are not that complex b) could increase familiarity with the codebase c) CI should do most of the code review. I know as an early stage contributor myself, I would be keen to scour the codebase, adding type hinting, and learning more about the structure of the project. --- [Visit Topic](https://discuss.tvm.apache.org/t/rfc-setting-up-mypy-type-checking-for-tvm-codebase/9231/14) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.apache.org/email/unsubscribe/eb52fbb537ebdcaf89db7e5b359b75f9f641f45b64a5231a3734bfdcf865c941).
