Klaus Alfert

@fenollp, I don't think so. Macros generate an AST and do not inject Elixir source code as Erlang macros would do. So, the first steps of source code analysis within...

The behaviour is not surprising at all, it is effectively the same situation we found in #30: * Propcheck finds a counter examples and stories it automatically * In the...

Aren't that two things, which should be handled independently: * a way of streaming the generated values out of the property * apply some kind of statistics, visualisation or similar...

Thanks, that works indeed. Here is the solution a bit reformatted: ```go genIntPair := func() gopter.Gen { return gen.IntRange(10, 20).FlatMap(func(v interface{}) gopter.Gen { k := v.(int) n := gen.Const(k) m...

I like your FlatMap -> Map approach. This boils down to ```go genIntPair := func() gopter.Gen { return gen.IntRange(10, 20).FlatMap(func(v interface{}) gopter.Gen { k := v.(int) return gen.IntRange(2*k, 50).Map(func(m int)...

Beneath state machine models I am most stunned by QuickCheck's Pulse subsystem to use property based testing for analysing concurrent algorithms and systems. Alas, it is available only in the...

Interesting idea for the Reporter! My gut feeling is that we need to exploit the Erlang trace API to get information about running processes and their messages. Putting these traces...

With Tracer, we would have explicit access to all messages send etc since we intercept them (similar to what Pulse does). No, I thought of using the tracing capabilities for...

Yes, reporting facilities from `assert` are really really nice. Perhaps we can tackle this the other way around: Perhaps we can replicate the code of assert (or even call it?...