The main topic of work has been:
- Increase code quality (I am still learning the language after all)
- Make the API reasonable
- Remove restrictions
On the latter subject, Croupier will now happily handle tasks with zero or many inputs, with zero or many outputs, or task that share some or all of their outputs, even if their inputs differ.
In all those cases it will try to Do The Right Thing, but it is arguable whether it does or not.
So, the API and what it can do is changing often. However the example in the README only needed one change from the first release to now (because it's pretty simple)
I know nobody is ever going to use it, it's a niche library in a niche language, but I am having fun writing it, and the concepts are quite widely applicable, so it's educational.