Add type hinting

I would suggest (though it is again stylist and not required) to start adding type hints as it is being moved into the standard python world. This helps many code editors with completion and allows for robust tests using type checkers such as mypy.

Though this is not my field, I can see this code as being a framework where other researchers import it and build future models, thus type hinting would keep them from stumbling over the various inputs and outputs related to theano and pymc3 which are vital to the functionality of the code. I note that neither of these frameworks are typed, but the size of exoplanet is manageable enough (with lots of contributors) to slowly add this in.

[dfm]

Great - yes, it really is awesome for code completion, etc. I have a few other projects (that don’t depend on numpy) where I’ve loved using Python typing.

I’m going to remove the joss label on this issue and leave it open as a future feature request. Hopefully sooner rather than later!

[dfm]

@grburgess: If you don’t mind, I propose splitting this into two issues: (1) Fill in some missing docstrings and (2) type annotations.

I would argue that type hinting is out of scope for now since the underlying libraries (numpy and theano/aesara) only have very limited support for typing at the moment (e.g. https://github.com/numpy/numpy/issues/7370 & https://github.com/pymc-devs/aesara/issues/200). Since these are the main return types of all of the exoplanet methods, I’ve found that the added benefit is currently somewhat limited. In the long run, I would very much like to add this so I’m following the conversations closely! What do you think about that @grburgess?