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
replace check_solve by check_solver_within_range #4715
Labels
Comments
I'll do the |
This was referenced Aug 8, 2017
Ugh, there are 135 occurrences left:
|
While I see the advantages in using the suggested function/macro, I think the fact that nobody has approached this problem for more than 6 years indicates that the remaining tests have been fairly robust nonetheless and we should close the issue for now, the work is simply not going to happen anytime soon, be this issue open or not. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Nowadays we have a nice little macro
We should replace all occurrences of
check_solve
at some point...Relates to #4704
The text was updated successfully, but these errors were encountered: