Is possible to handle tests being killed with prog: <<loop>> by the RTS? Now Hedgehog just dies, but it would be great to report the input that causes the test to be killed and proceed with other tests. Right now looping tests cause thread blocked indefinitely in an MVar operation exception, so I guess it should be possible to handle it in some reasonable way.
Is possible to handle tests being killed with
prog: <<loop>>
by the RTS? Now Hedgehog just dies, but it would be great to report the input that causes the test to be killed and proceed with other tests. Right now looping tests causethread blocked indefinitely in an MVar operation
exception, so I guess it should be possible to handle it in some reasonable way.