Klaus Alfert

Hi @kostis , can you give us a rough time plan when you expect to be able to create a release? If this is not yet possible, that would also...

Very cool, @kostis! Our CI tests are looking very good. 👍

Thanks @kostis and @ferd! The PropCheck tests are green, so no obvious problems on Elixir side. I am happy to release the new features to the Elixir world.

Hi @pallix , nice catch, this is similar to #112. We should warn about that in the documentation. Since propcheck relies heavily on macros and code generation, it could be...

That is an interesting idea. `conjunction` is implemented in `proper` as specific part of all properties, including data generation etc (starting here: https://github.com/proper-testing/proper/blob/bfd7d862dd5082eeca65c192a7021d0e4de5973e/src/proper.erl#L1151). I assume (gut feeling only) that a...

Hi @drselump14 , thank you for your PR, but I guess you are solving the problem at a wrong place: PropEr and thus PropCheck require a boolean return value. `assert`...

@adkron, I guess you are omitting something. To put your example in a full property I did this ```elixir property "let with pos_integer fails", [:verbose] do our_list = let count...

Ouch, that feels like too many levels of abstractions :-) if I understand your statement correctly. The tuple return value of `produce/2` can do all kinds of surprising things ...

I can support this, also floats do not work. Binaries are not problem. Since PropCheck delegates to the PropEr for the implementation of of the generators, I assume that we...

I like the idea of putting some functions in a "interactive" or "console" package. `produce()` belongs there, `sample_shrink()` also. `quickcheck()` is also a candidate, as are the reporting functions like...