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.
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.