Olivier FAURE

Pinging this. It would be really useful to be able to set up simple "send strings in, check what gets out" tests with Vorpal.

Error messages: ``` error: failed to run custom build command for `fuzzcheck v0.11.0 (https://github.com/loiclec/fuzzcheck-rs#8f7de6fa)` Caused by: process didn't exit successfully: `/home/olivier-faure/Documents/venial/target/fuzzcheck/fuzzing/build/fuzzcheck-79c9b2bdd54171d2/build-script-build` (exit status: 1) --- stdout TARGET = Some("x86_64-unknown-linux-gnu") OPT_LEVEL...

I managed to get it running with the following commands: ```sh $ nix-shell -p rustup $ cargo +nightly fuzzcheck fuzz::fuzz_parse --profile fuzzing ``` But now I have the same error...

Is there progress on this issue? The approach suggested by @CreepySkeleton seems pretty good to me. If the issue is stalled for need of a contributor, I'd be interested in...

> For more general ADTs, such as a `Either a b = Left a | Right b`, that could desugar to a C++-style: > > ```c++ > enum EitherTag {...

> The caller somehow knows that it is receiving an owned string and cooperates by calling back into the module again after its copy of the string is constructed to...

To make sure everyone's on the same page, here's my current understanding of the planned implementation of outgoing slice returns. First off, we want a scheme that is as simple...

Adding myself to the list of interested users. I found this repository while looking for a simple way to add caching to my crate's CI. I would absolutely adopt this...

Keep in mind there's a lot on everyone's plate. Sometimes you have big ambitious project ideas, and when you start working on them you realize there's a lot of foundational...

I think a sufficiently advanced implementation would get the best of both worlds anyway, e.g. use the "multiple return values" approach when the catching code is close to the throwing...