avoid sortedness errors with polymorphically let-bound constants #544
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.
Fixes bug 1 of #542 by providing a fast path for constants in
getResultSort
that also does not assert a condition that isn't true for let-bound constants.A TFX1
$let
might capture sort variables. Consider e.g. polymorphic lists and the following axiom.In the expression
e
,x: list(A)
. But this is a non-polymorphic constant (both term and type arity 0) with a variable in its result sort, whichSortHelper
doesn't like. It seems to be eliminated just fine in later FOOLing around.