Think about combining repositories into cargo workspace

[lbirkert]

This would allow us to fix & test bugs more quickly, who are introduced by a local dependency of the rustpotter family, as we are not depending on crates.io (which requires a new version to be published before such an issue can be fixed).

[GiviMAD]

Right now I'm relying on changing the cargo dependency while developing.

But yes it will probably make things easier, I think that keeping the library in a separate repo and having another one with all the other tools and the library as a submodule is the option I like more. I think I can place that repo at https://github.com/rustpotter.

I will try to look at it when I have a moment.

I'll like also to investigate if libraries for other languages can be develop in an "easy" way, there are some tools I would like to investigate like wasmtime, but I haven't found the time to look a it. But having all in a repo which people can PR to seems a good idea in case someone wants to work on supporting a new language.

[GiviMAD]

At the end I'm not so convinced to change it to a workspace.

I think it can be too much code from different languages in the same repo, and I see some advantages on it but I also with the flexibility offered by cargo for installing from local folders or git repositories I don't see it like something needed.

I'm still thinking on it, but with the amount of work I have at the moment don't think I can do it for now either way.