emil-e

I do not have any plans to do it currently. I never intended RapidCheck to be used as a shared library so I'm not sure it would make sense to...

I see, sounds reasonable. Well, if you make a PR for this that looks good, I'll happily merge it!

I don't currently have any plans of versioning but it's not ruled out in the future.

RapidCheck in an of itself only provides a very barebones "test framework". If you want something like this, I'd recommend you use something like Catch, Google Test or Boost Test...

The documentation on how to implement custom generators is, admittedly, lacking. Since I do not get paid for working on RapidCheck, documentation on more advanced topics has taken a backseat....

`rc::detail::ImplicitParam::value() != rc::detail::CurrentPropertyContext::defaultValue()` will be true if you are in a property. I would welcome a pull request for at least a function that can be used for checking this.

Sure. You want to catch `CaseResult` which you can see at https://github.com/emil-e/rapidcheck/blob/b67174625b791105bb98ca58f329bd101bf261ee/include/rapidcheck/detail/Results.h#L17 `description` contains the message.

I always knew this was the case but I never thought it would actually happen based on the low probability. Do you have any suggestions for solutions?

Yes, this would indeed be a useful feature but I rarely have time to work on RapidCheck these days. I do welcome a PR though, and I will spend time...

I think you could solve this by saving the last seen actual failure result and simply use that. However, the problem is that shrinking will be slower since you will...