Skip to content

fixing genericCoarbitrary #99

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

Merged
merged 1 commit into from
Dec 5, 2020
Merged

Conversation

athanclark
Copy link
Contributor

coarbitrary is intended to perturb an unrelated Gen with data that implements the typeclass - it's not intended to be explicitly related to the generated data.

@hdgarrood
Copy link
Contributor

Seems sensible to me. I wonder if we should regard this as a breaking or minor-level change though, as it's possible someone was relying on the more specialized type for type inference. Admittedly that possibility seems a bit remote.

@athanclark
Copy link
Contributor Author

athanclark commented Mar 8, 2019

I think it should probably be a hard version change rather than minor; because the type signature clearly changes. However, anyone using the function would be restricted to site-based usage, in which the generator perturbed would be of the same type as the indexed value - such that, if replaced by my more general version, it should still compile a-ok.

@JordanMartinez JordanMartinez merged commit b7f47a6 into purescript:master Dec 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants