You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the other hand, catching all the exceptions would interfere with timeout handling code, as explained in the comment. (In fact, your changes to smallcheck & quickcheck probably interfere with it already, I just didn't realize that.)
The text was updated successfully, but these errors were encountered:
Because System.Timeout.timeout throws an exception, but will be unable to catch it back. The exception will still abort the computation, but the message will be different.
Hey @nomeata. I'm looking at tasty-hunit code in connection with the policy that you proposed. In d1d417c you said that HUnit sas already catching exceptions. But in fact it only catches HUnitFailure exceptions (https://github.com/feuerbach/tasty/blob/master/hunit/Test/Tasty/HUnit.hs#L52). Doesn't that contradict your policy?
On the other hand, catching all the exceptions would interfere with timeout handling code, as explained in the comment. (In fact, your changes to smallcheck & quickcheck probably interfere with it already, I just didn't realize that.)
The text was updated successfully, but these errors were encountered: