Add typings

We should add typings to manim:

1. It allows for more precise intellisense and easier-to-check code (via mypy and whatnot);
2. It ensures we follow a structure that makes sense (i.e., ensures we don’t have a data model in which people get completely lost);
3. Writing documentation and specifying types are tied to each other. When we work on documentation, it is inevitable that we will specify types for things, so why not add it to the code as well?

Notes:

1. We can use stubgen to have a headstart;
2. We can use stub files in order to keep typings separate from the code and not have to change things much (but this is debatable - please expose your opinions on this);
3. This is very related to the dataclasses solution proposed in #7, and may ultimately be a consequence of it.

Thoughts?

[PgBiel]

@PgBiel I meant having in-code and not having in-docstring.

got it

What is the benefit of having both? All I could think of is that a user reading the docs might not get the full benefit from in-code, but if Sphinx can be configured to parse in-code and show those to the user, then why bother?

if we can configure that, then it should be fine The only thing that we have to note is that, at the moment, we aren’t adding typehints in code, so they must be added in docstring for now Then a future typings PR may move them from the docstring to the code, and we may have simpler docstring types.

[behackl]

Seems like this never went anywhere? Bit of a shame. Makes it way harder to learn for beginners.

It’s work in progress. Type hints have been added to some parts of the library; help for adding them to other parts is warmly welcome.