This repository has been archived by the owner on May 15, 2021. It is now read-only.
as patterns on both sides #519
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
facebook-github-bot
added
the
CLA Signed
mheiber
approved these changes
Feb 19, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 is the first step/example of taking "the smart direction" in bidirectional type-checking.
Before:
Being "structurally/semantically" equivalent, - they produced different outcomes because of "left -> right" flow of checking.
Now we treat them the same way, -> forcing type-checker into more complicated pattern first (which is likely to produce more information).
It may also be seen as an opening of starting discussion of IR, - since we can just get this specialisation/normalisation in IR when translating from abstract forms.