Refactoring: Make the state of type forward references explicit #4092
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
Forward references can be either unbound or resolved. Also ensure that each forward reference is only resolved at most once. As a semi-related change, be more careful about forward references leaking after semantic analysis.
|
A related note: as I mentioned in #3952 (comment) some double-forward references still don't work (stay unresolved/unbound). This is because third pass happens only once. In |
|
Let's not care about this yet. We have bigger fish to fry. Can you add an issue to track this? |
Opened #4095 |
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.
Forward references can be either unbound or resolved. Also ensure
that each forward reference is only resolved at most once.
As a semi-related change, be more careful about forward references
leaking after semantic analysis.