arbitrary icon indicating copy to clipboard operation
arbitrary copied to clipboard

Generating structured data from arbitrary, unstructured input.

Results 31 arbitrary issues
Sort by recently updated
recently updated
newest added

Sometimes a field of a struct doesn't implement arbitrary and it is either impossible to do (because it is from another crate, for example) or undesired. We should support some...

enhancement

Hello, I've been toying with custom mutators in cargo-fuzz with libfuzzer and it seems to me to support changes to typed data instead of bytes, the reversed arbrirtary operation would...

I was able to get `0` out of `int_in_range(1..=i32::MAX)`, which is less than the minimum specified value of `1`! Here's what I think is happening in `int_in_range_impl`: * Suppose when...

Hello! Bear with me as I am new to Arbitrary. I have this type from [juniper](https://github.com/graphql-rust/juniper): ```rust pub struct Arguments, Spanning)>, } ``` `Spanning` and `InputValue` successfully `derive(arbitrary::Arbitrary))`. When I...

In our use case, we are not using Arbitrary for fuzzing, but simply for creating arbitrary fixture values in tests. Currently we create a 10MB static `Vec` of random noise...

This PR solves issue #44 by implementing a `dearbitrary` function to create a byte buf, which can be used again with `arbitrary` to recreate the struct. It is not a...

Sometimes you don't want more than N things generated because, for example, it makes the fuzz target too slow and run up against libfuzzer timeouts. A solution to this is...

This adds a "std" feature that enables support for compilation with std. Without this feature, the library becomes compatible with #![no_std] crates. By default, the library compiles with support for...

For example, the following code (using version `1.0.1`) fails to compile. ```rust use std::borrow::Cow; #[derive(arbitrary::Arbitrary)] pub struct WithACow { cow: Cow src/main.rs:3:10 | 3 | #[derive(arbitrary::Arbitrary)] | ^^^^^^^^^^^^^^^^^^^^ | note:...

https://github.com/rust-fuzz/arbitrary/commit/1d2f65360f634968b5525f4d6430a88a376277f0 > Next breaking release that we make, I think we can remove the fallibility from the `Arbitrary` trait and all the `Unstructured` methods. This wasn't addressed in the discussion...