Cameron Elliott

Results 69 issues of Cameron Elliott

First, both rust fuzz and the book are freaking awesome! Thanks for creating both!! As an outsider, I wanted to share some experiences which might help improve the book, and...

Again, thanks to the creators of both the fuzzer and the book. They are both great. I ran through this tutorial on two systems: https://rust-fuzz.github.io/book/cargo-fuzz/coverage.html While using the rust-url project...

Hey, thanks for writing this book! I had an issue with vscode where editing files inside ProjectZ/fuzz/fuzz_targets/targetX.rs wasn't working with or providing me any Rust Analyzer feedback. I figure out...

From the README > Currently this module is not 'safe' because Bufs can outlive the memory pool they are associated with. I believe fixing this will require adding an Arc...

While not strictly needed to use this cool program, it would really add some value if the source of the shard failure rate for both the examples of invoking this...

It looks like there is a little extra junk in the Readme: ``` $ python durability.py 4 2 0.10 1python durability.py 17 3 0.00405 6.5 ``` Probably that first invocation...

This is a nice piece of work! I re-integrated the benchmarks from the README into the _test file, and here is what I got on an AMD64 Mac mini. ```...

Thanks for writing this program, it's great! When running 'testing' ReadTest(...), I got this seg violation, not sure of the root cause, didn't investigate deeply. This occurred on a AMD64...

While --uses might not seems as logical under the `structure` sub-command as the `dependencies`, I think it could be useful for some people. On the project I am working on,...

The documentation reports that `#![feature(generators, generator_trait, try_trait)]` is required. In recent Rust releases, try_trait has been removed, and try_trait_v2 has been added.