uxarray has some type hinting in general but the coverage is incomplete, as mentioned in #1763. In many cases return types are missing.
This issue would be fully resolved when all functions have return type annotations… which sounds like a pretty big task. I am guessing it would make sense to break this up into sub-issues, each handling one part of the code, maybe one sub-issue per subpackage (like uxarray/core, uxarray/io, …) or even finer-grained resolution if necessary to make things easier to review?
@rajeeja after looking into the type hints a bit with your post of #1763, do you have any recommendations for what order to prioritize these issues? In particular, does it make sense to add any automated type-checking tests which are sensitive to return type (e.g. --disallow-untyped-defs) before starting on this issue? Or, would it make more sense to do a "best-effort" approach at first, and then test correctness and fix any bugs at the very end?
uxarray has some type hinting in general but the coverage is incomplete, as mentioned in #1763. In many cases return types are missing.
This issue would be fully resolved when all functions have return type annotations… which sounds like a pretty big task. I am guessing it would make sense to break this up into sub-issues, each handling one part of the code, maybe one sub-issue per subpackage (like uxarray/core, uxarray/io, …) or even finer-grained resolution if necessary to make things easier to review?
@rajeeja after looking into the type hints a bit with your post of #1763, do you have any recommendations for what order to prioritize these issues? In particular, does it make sense to add any automated type-checking tests which are sensitive to return type (e.g.
--disallow-untyped-defs) before starting on this issue? Or, would it make more sense to do a "best-effort" approach at first, and then test correctness and fix any bugs at the very end?