-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deriver: first release #192
Comments
I'd propose to not require #191 for the first release. I currently have the time to solve multiple issues in that list, but, unfortunately I don't think I can right now do #191. However, I think this should not be blocking for a first release, shrinkers are great yes, and we will derive them as well, but generators would be a great first feature. |
As I wrote elsewhere I think only #188 is required before a release (from my POV) |
Required yes maybe. It will work for QCheck2, but it's a bit unfortunate to restrict the deriver to the new version only I think |
Any updates on this? Is there something a new contributor could help with? So far I am a happy user of |
We should not be far away from a first release. There is two open merge request regarding the deriver:
The first one should be closed pretty easily, once @jmid and I agree on the patch. The second one however contains a lot of boiler-plate code. Reviews/tests/inputs would be more than welcome to help the maintainers in a potential merge. |
Closing as we already had a first release of |
I have opened several issues that I believe should be fixed before we release the deriver.
Feel free to add if I missed something :)
The text was updated successfully, but these errors were encountered: