quickcheck Printing is slow!

Printing is super expensive; I just ran a property where each test case takes very little time. 200 000 tests took 14 seconds, but 200 000 tests with chatty = False took 4 seconds. Such a huge penalty for just printing!

chatty = False is not always ideal, as I am interested in the current progress of my property. There should be some half-way option where I can ask for output, but less. I am just not interested in unperceived updates :) I have a patch ready to go for this, but I document this here so that this is not forgotten.

Mar 30 '23 12:03 Rewbert

We need an FPS limiter! :D

Mar 30 '23 12:03 nick8325

For slow tests the current implementation is fine (execution time is not dominated by printing), but for fast ones we need an FPS limiter! :)

Mar 30 '23 13:03 Rewbert

In the parallel fork of QC, this is not a problem. The final design might change, but something will be done about this in 2.16.

Apr 25 '24 11:04 Rewbert