I refined existing type annotations in #671, but I also found some deep inconsistency with Coordinates._mesh_reduction's return type: the return array can contain a mixture of 2D arrays and a single 1D one representing a normal. I'm willing to bet this was never consciously designed this way, but there seems to be at least some level of coupling with the rest of the module, so fixing it is not trivial.
I don't think I want to delay 0.20.0 over this, but I also don't want to forget about it.
I refined existing type annotations in #671, but I also found some deep inconsistency with
Coordinates._mesh_reduction's return type: the return array can contain a mixture of 2D arrays and a single 1D one representing a normal. I'm willing to bet this was never consciously designed this way, but there seems to be at least some level of coupling with the rest of the module, so fixing it is not trivial.I don't think I want to delay 0.20.0 over this, but I also don't want to forget about it.