Skip to content
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

tasty-quickcheck exports different things depending on the underlying QuickCheck version #208

Open
quasicomputational opened this issue Jan 19, 2018 · 1 comment

Comments

@quasicomputational
Copy link

tasty-quickcheck re-exports QuickCheck's API wholesale, and has a loose version bound on the underlying QuickCheck library. This means that a single version of tasty-quickcheck can have a different API depending on the underlying QuickCheck version, which is a pain for consumers: if I am using something added in a recent QuickCheck, I have to add a dependency on QuickCheck just to ensure that the new feature is present in tasty-quickcheck, even if I never import from QuickCheck directly!

Please consider either explicitly enumerating the re-exports, or precisely fixing the QuickCheck version that tasty-quickcheck depends on.

@UnkindPartition
Copy link
Owner

Fair enough; I'd accept a PR that enumerates the re-exports explicitly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants