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.
Changes:
evar X T Y
. The point is that Y can occur elsewhere, and unif can restrict it. The CHR rule for UT uses Y's scope to operate, and if X is larger we don't know what to do. So we immediately restrict X whenever Y is.Todo:
type loc loc -> term -> term
would be step 0, the one would need a more efficient implementation ofsafe
or some auxiliary API to close wrt the context, since now it only supports ground terms, eg strings, but during elaboration one may want to just store the (non-ground) data needed in order to print an error (for efficiency). Syntactic Constraints kind of do that, but how to use them is not 100% clear yet (they key is simple, but not ground either, unless you don't key them...)