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
nsatz
no longer unfolds TwoF
#18872
Comments
Thank you @thery for spotting the problem :) |
I'd guess it's #18325 -- previously nsatz interpreted goals using typeclass search, which I believe would have unfolded TwoF. IMO the nsatz change itself here is likely desirable as it makes it easier to predict whether nsatz will solve a goal and makes nsatz less slow on pathological cases, but breaking scripts that relied on the heuristic unfolding is unfortunately direct consequence. Currently, the main way we offer for handling changes of this kind is to participate in the Coq CI. There have been a number discussions about how strict and conservative we should be about avoiding coq changes that require backwards-compatible changes to downstream code, and input is welcome in that regard. |
So is
|
Yes, |
maybe something should be added in the change log if it is not already done explaining this issue and the possible change of behavior of |
Description of the problem
I recently had to change our script to get our library to compile with Coq 8.19.0.
Small Coq file to reproduce the bug
Version of Coq where this bug occurs
8.19.0
Last version of Coq where the bug did not occur
8.18.0
The text was updated successfully, but these errors were encountered: