emil-e

I haven't looked closely yet but I have one question at least. The splitting of run/verify is to more easily provoke race conditions? As it is now, the run function...

I've thought some more about this and I've understood the problem a bit better. I stumbled upon something that will likely be an issue: Originally, commands had to always assert...

No, I am aware of this and my concern is one specific to how RapidCheck is implemented. Consider the following command: ``` C++ struct Remove : public state::Command { std::string...

It seems like you are declaring your `Arbitrary` specialization in the namespace `::key_properties::rc`, it needs to be `::rc`.

You probably don't want to use `operator*` at all in this case. If you look at `Gen.h` you can see that it's also a function object that takes a `Random`...

As you say, filtering using `suchThat` is potentially expensive and should only be used when you don't have to discard too many test cases. For integers, you can use the...

You can read about it here: https://github.com/emil-e/rapidcheck/blob/master/doc/generators.md The user guide has links to pretty much everything: https://github.com/emil-e/rapidcheck/blob/master/doc/user_guide.md

Sorry about the late reply, vacation and stuff. Maybe this was unclear but to explicitly use a generator, "dereference" it using `operator*`.

I'm not sure I'm following. Can't you just assert for all of them in the same property lambda?

I don't think this is a bad idea per se but it's hard to implement since RapidCheck cannot know that there are tags that haven't been used. Also, a test...