is there any way to tell test.check to give up and just show me the smallest failing result so far after a certain number of iterations?

I've got one failure that I'm having a really hard time tracking down, but it'll run for 100k iterations without settling

@mattly there are a couple tickets surrounding that

@mattly there is also a callback function you can register on the master branch, that would let you "listen" for things as it's shrinking

there's a ticket for a max-shrink-time option, and for capturing C-c interruptions and returning the smallest value so far

I think the latter one is hairy though so I don't know if it will get implemented :/

C-c would probably be the most useful, so if it turns out to be straightforward I would love to add it

if it's hairy it's probably because of varying details in different repls vs. unix signals when running test processes and that sort of thing

oh fun