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

Module Test.QuickCheck.Instances collides with a module of the same name from checkers #9

Open
sol opened this issue Nov 1, 2014 · 4 comments

Comments

@sol
Copy link

sol commented Nov 1, 2014

From a users perspective this is a pain, esp. when using a global package database and GHCi. checkers was first, quickcheck-instances is more widely used. Not sure how to resolve this.

@aslatter
Copy link
Owner

I'm okay deferring to checkers after a deprecation cycle, although I'm not sure what a good window is to leave my version of Test.QuickCheck.Instances around.

I also wouldn't mind moving to a less "official sounding" module - something like Test.QuickCheck.Util.Instances or Test.QuickCheck.Contrib.Instances.

Pinging @nick8325 to see if they have any preferences.

@sol
Copy link
Author

sol commented Dec 15, 2014

Looking at checkers again, it also uses module names like Test.QuickCheck.Utils. I would tend to solve this in checkers and move everything from Test.QuickCheck.* to Test.Checkers.* (with a deprecation cycle of course). @conal what do you think?

@russmatney
Copy link

Is there are movement on this issue? I just ran into it, but it seems quite old - if there's a systemic way to solve this I'd love to know about it!

@russmatney
Copy link

Just discovered PackageImports, which totally solved this for me.

import "quickcheck-instances" Test.QuickCheck.Instances()
import "checkers" Test.QuickCheck.Instances()

Sorry for the noise!

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

No branches or pull requests

3 participants