Databases
StackOverflow2013
Postsdbo
POWhere do QuickCheck instances belong in a cabal package?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhere do QuickCheck instances belong in a cabal package?
    primarykey
    data
    text
    <p>I have a <a href="https://github.com/acfoltzer/nbt" rel="nofollow noreferrer">cabal package</a> that exports a type <a href="https://github.com/acfoltzer/nbt/blob/master/src/Data/NBT.hs" rel="nofollow noreferrer"><code>NBT</code></a> which might be useful for other developers. I've gone through the trouble of defining an <code>Arbitrary</code> instance for my type, and it would be a shame to not offer it to other developers for testing their code that integrates my work.</p> <p>However, I want to avoid situations where my instance might get in the way. Perhaps the other developer has a <a href="https://stackoverflow.com/questions/5643360/how-do-you-override-haskell-type-class-instances-provided-by-package-code">different idea</a> for what the <code>Arbitrary</code> instance should be. Perhaps my package's dependency on a particular version of QuickCheck might interfere with or be unwanted in the dependencies of the client project.</p> <p>My ideas, in no particular order, are:</p> <ul> <li>Leave the <code>Arbitrary</code> instance next to the definition of the type, and let clients deal with shadowing the instance or overriding the QuickCheck version number.</li> <li>Make the <code>Arbitrary</code> instance an orphan instance in a separate module within the same package, say <code>Data.NBT.Arbitrary</code>. The dependency on QuickCheck for the overall package remains.</li> <li>Offer the <code>Arbitrary</code> instance in a totally separate package, so that it can be listed as a separate test dependency for client projects.</li> <li>Conditionally include both the <code>Arbitrary</code> instance and the QuickCheck dependency in the main package, but only if a flag like <code>-ftest</code> is set.</li> </ul> <p>I've seen combinations of all of these used in other libraries, but haven't found any consensus on which works best. I want to try and get it right before uploading to Hackage.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USacfoltzer
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhere do QuickCheck instances belong in a cabal package?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhere do QuickCheck instances belong in a cabal package?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhere do QuickCheck instances belong in a cabal package?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COPerhaps the fact that you *have* seen all of these approaches used indicates that there actually *isn't* a consensus? Or at least not a one-size-fits-all solution.
      singulars
      1. POWhere do QuickCheck instances belong in a cabal package?
      1. USC. A. McCann
    2. CO@C. A. McCann: certainly, and that would be a valid answer. It seems worth a discussion, though.
      singulars
      1. POWhere do QuickCheck instances belong in a cabal package?
      1. USacfoltzer
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload