Take a look at xtask. It essentially relies on the fact that you can add cargo aliases in local files in order to execute specific packages.
When I create a workspace that has some form of code generation I like to overwrite cargo gen to whatever is doing the generating.
Number 4 is only about not returning impl Into and instead just returning T.
That’s a bummer. I guess what I though was PyO3 type hints was actually just PyCharm guessing at the types.
I tried creating a .pyi file and it seems to be a pretty big improvement over no type hints, but I don’t know how to add type hints for modules added with PyModule::add_module and adding the .pyi file seems to make the type checker not know about my other modules.
Would you mind sharing the script for auto generating type hints? Keeping them in sync manually would be pretty annoying.
How is the quality of the generated bindings?
I have previously used PyO3 for Python bindings and it doesn’t seem to correctly generate type hints.
I have used cargo ramdisk before with success.