[DSLX] Fix use of a type instantiated in a alias.
#1882
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
cdleary
force-pushed
the
cdleary/2025-01-23-use-syntax-type-alias
branch
from
2455155 to
8bf031c
Compare
cdleary
force-pushed
the
cdleary/2025-01-23-use-syntax-type-alias
branch
from
8bf031c to
75b7f5e
Compare
meheff
approved these changes
Jan 24, 2025
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.
Fix for the scenario where we use a type definition into the module scope and then instantiate it in a type alias. Add a
dslx_lang_testfor this.Note that this adds
UseTreeEntryas a node that can be aTypeDefinition.Progress towards #352