Deprecated

barecheck

QuickCheck implementations for common types

http://github.com/massysett/barecheck

Version on this page:0.2.0.6
LTS Haskell 1.15:0.2.0.8
Stackage Nightly 2015-03-19:0.2.0.6
Latest on Hackage:0.2.0.8

See all snapshots barecheck appears in

BSD-3-Clause licensed and maintained by Omari Norman
This version can be pinned in stack with:barecheck-0.2.0.6@sha256:4a6515a0d1955aba60c920ae6edba2664e85f404d5772e90cf185be61fb0689b,3247

Module documentation for 0.2.0.6

  • Barecheck
    • Barecheck.Promote
    • Barecheck.Util
  • Data
    • Data.Map
      • Data.Map.Coarbitrary
      • Data.Map.Generators
      • Data.Map.Shrinkers
    • Data.Monoid
      • Data.Monoid.Coarbitrary
      • Data.Monoid.Generators
      • Data.Monoid.Shrinkers
    • Data.Sequence
      • Data.Sequence.Coarbitrary
      • Data.Sequence.Generators
      • Data.Sequence.Shrinkers
    • Data.Text
      • Data.Text.Coarbitrary
      • Data.Text.Generators
      • Data.Text.Shrinkers
    • Data.Time
      • Data.Time.Coarbitrary
      • Data.Time.Generators
      • Data.Time.Shrinkers
    • Data.Tree
      • Data.Tree.Coarbitrary
      • Data.Tree.Generators
      • Data.Tree.Shrinkers
  • Prelude
    • Prelude.Coarbitrary
    • Prelude.Generators
    • Prelude.Shrinkers
Used by 2 packages in lts-0.7(full list with versions):
quickpull, rainbow-tests

Provides QuickCheck implementations for common types distributed with GHC and in the Haskell Platform. The implementations are NOT provided through the QuickCheck Arbitrary and CoArbitrary typeclasses; instead, they are provided through ordinary, non-overloaded functions. This avoids problems with orphan instances.

Implementations are provided through child modules of the module that provides the original type. For example, for Data.Map, look under Data.Map.Generators, Data.Map.Shrinkers, and Data.Map.Coarbitrary. For instance, a function that generates a Map is at Data.Map.Generators.map, while a function providing a coarbitrary implementation is at Data.Map.Coarbitrary.map. Obviously this can lead to name conflicts, both between modules provided in this package and with other standard modules, so keep this in mind when you do your imports.