Bugfix: normalize SAW core types when necessary to type elimination forms #1426
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 fix addresses issue #1420, where the type-checker does not normalize the types of globals when it tries to type-check applications or pair or record projections. For example, the definitions
will fail to type-check, because the type of
myId
is not normalized to a function type whenmyId
is applied tox
.The fix is to update calls to recognizers
asSort
,asPi
,asPairType
, andasRecordType
in the type-checker so that the types passed to these recognizers are normalized when the recognizers fail.