attach orig-binding property (used for occurrence typing) #10
Conversation
This file contains hidden or 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
AlexKnauth
force-pushed
the
occurrence-orig-binding
branch
from
57b2d63 to
d90dbbf
Compare
Collaborator
Author
|
Closing because #12 is better for the current implementation of occurrence typing. |
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 pull request changes the
inferfunction so that when it's introducing variables into the environment, it attaches an extra property so that other rules can find the original variable with the original scopes. This is used for occurrence typing.Is this the right way to do this? What if one of the attached
sepproperties happens to be the nameorig-binding?