-
Notifications
You must be signed in to change notification settings - Fork 587
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hypothesis doesn't tell me when a rule never assumes something successfully #213
Comments
To summarize some discussion from IRC: It's almost impossible to solve this perfectly. The problem is that for strategies with lots of rules, the chances are very high that at least one will not get properly exercised in a given run, which means that if you have a bunch of perfectly reasonable assumes some of them will probably fail to ever pass in a given run. This means that simply failing if any rule never passes its assumptions is error prone to say the least. However not doing anything about this is a major usability issue, so I'm going to try to figure out how to make this better, but it's unlikely that it can be made perfect. |
Closed by the new |
I don't think so? The problem here is with rules that are not supposed to be run after every step, but should still sometimes run. |
I think emiting a warning for each precondition which was never satisfied would be more reasonable, since we notionally check each of them before each step. master...Zac-HD:report-unsat-preconditions suggests to me that this should only run once, i.e. at the end of the |
Closing this issue in favor of the list of observability ideas linked above 🙂 |
I expect this program to raise an exception because the
okay
rule never successfully runs:The text was updated successfully, but these errors were encountered: