Conditional rules#1438
Open
bodeveix wants to merge 14 commits into
Open
Conversation
This file contains hidden or 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
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 extends the syntax of rules to add optional equational constraints of the form:
rule <term> when <term> ≡ <term> ↪ <term>rule <term> when <term> «[op] <term> ↪ <term>In the first form, the compared terms must be flat, i.e. of the form
f $p1 ... $pnto avoid cyclic dependencies between files.In the second form, the compared terms are restricted to pattern variables. The condition is satisfied if the valeur of the first is a sub term of the value of the second one by crossing only
oparguments. Subterm conditions could be expressed using the first form, but it would need defining a sub term relation for each operator.Remarks: