Crates.io | proptest-arbitrary |
lib.rs | proptest-arbitrary |
version | 0.2.2 |
source | src |
created_at | 2017-09-19 01:38:39.06744 |
updated_at | 2018-01-08 12:15:05.577511 |
description | The Arbitrary trait for proptest and implementations for the standard library. |
homepage | |
repository | https://github.com/Centril/proptest-arbitrary |
max_upload_size | |
id | 32212 |
size | 113,012 |
NOTE: This version is still WIP; don't use yet, just reserving at crates.io.
Proptest is a property testing framework (i.e., the QuickCheck
family)
inspired by the Hypothesis framework for
Python.
This crate, proptest-arbitrary
, additionally provides an
Arbitrary
trait which allows you to have a canonical Strategy
per type. This is the equivalent of Haskell QuickCheck's implementation
of Arbitrary
. In this interpretation of Arbitrary
, Strategy
is the
equivalent of the Gen
monad.
Arbitrary is currently implemented as:
/// Arbitrary determines a canonical Strategy [..]
pub trait Arbitrary<'a> : Sized + Debug {
fn arbitrary() -> Self::Strategy {
Self::arbitrary_with(Default::default())
}
fn arbitrary_with(args: Self::Parameters) -> Self::Strategy;
type Parameters: Default;
type Strategy: Strategy<Value = Self::ValueTree>;
/// NOTE:
/// This type should NOT be relied upon outside of this crate
/// other than for implementing `Arbitrary` for other types.
type ValueTree: ValueTree<Value = Self>;
}
This crate is currently experimental. It will hopefully be included in
proptest
in the future.
The current definition of the [Arbitrary] trait might change in the future pending the development of existential types in Rust. However, as long as you don't rely on Arbitrary having associated types in calling Arbitrary, in practice, this should not be a problem.
This crate mostly just contains Arbitrary and implementations for it. Therefore, it is unlikely to see breaking change. If any change occurs, it will likely be new implementations or newtypes around common types.
See the changelog for a full list of substantial historical changes, breaking and otherwise.
TODO
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.