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
When debugging a failing case produced by qcheck-lin, it would be nice if dscheck could explore only the interleavings that produce the same intermediate values as reported by qcheck-lin (and skip the other execution traces that are less likely to have a bug). I think it would be enough to raise a specific exception to indicate that we don't need to continue exploring that way: (but not report it as a failure)
if value <> expected then raise Dscheck.Skip ; (* ... *)
(It almost works if the user does the try...with Skip -> () on their side, because the final postcondition is still called)
The text was updated successfully, but these errors were encountered:
When debugging a failing case produced by
qcheck-lin
, it would be nice ifdscheck
could explore only the interleavings that produce the same intermediate values as reported byqcheck-lin
(and skip the other execution traces that are less likely to have a bug). I think it would be enough to raise a specific exception to indicate that we don't need to continue exploring that way: (but not report it as a failure)(It almost works if the user does the
try...with Skip -> ()
on their side, because thefinal
postcondition is still called)The text was updated successfully, but these errors were encountered: