Type checking with new VarType #140
Open
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
mikeday
force-pushed
the
mikeday/typevar
branch
4 times, most recently
from
7502ca7 to
d6009ac
Compare
mikeday
changed the title
mikeday
force-pushed
the
mikeday/typevar
branch
from
d6009ac to
8ef87b6
Compare
mikeday
force-pushed
the
mikeday/typevar
branch
from
8ef87b6 to
58f9f6d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 does proper (?) unification, including aliasing variables X = Y, but without an occurs check as I don't think (??) that X = f(X) can happen during type checking.