Fix equality on external aequiv for symbols #5
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.
When we generate equivalence functions for ABTs that utilize symbols, the internal comparison works as expected since symbols are internally
unit Abt.t
which can be compared usingAbt.aequiv
.However, generated external
aequiv
fails to compile because it still usesAbt.aequiv
to compareTemp.t
when it should useTemp.equal
. This patch remedies the bug, which seems to have been introduced in 02b8f27.In the following example, we have:
Before patch:
After: