Adapt to Coq PR #18007: Proof_using.definition_using takes names of fixpoints being built #513
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ecursive definitions as extra arguments.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is to adapt to Coq PR #18007. Its purpose is to ensure that the kernel does not receive names that are not available in the section.
When building fixpoints, the named context contains the name of the fixpoints being built (not sure this is a good way to do but it is how it is done now). So, we need to tell Proof_using.definition_using to exclude these variables.
Afaiu, the call to Proof_using.definition_using in coq-elpi is about a regular (non-recursive) definition, so the list of fixpoints names is []. I hope I did not misunderstand.
In any case, this is to be merged synchronously with coq/coq#18007.