Unbound variable check when internalising module #548
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.
Check whether all existential variables are quantified when internalising rules. This is to prevent runtimeverification/haskell-backend#3777, where the rule contains a variable on the RHS which does not appear on the LHS and should therefore be existentially quantified, since this is the assumption that the booster currently makes and we leak internal variable names when this assumption is violated (we could drop using explicit
\exist
altogether and just infer exist variables automatically).With this change, sending this request:
will result in the following error: