-
Notifications
You must be signed in to change notification settings - Fork 64
feat(infer): resolve nested table literals as Instance types #987
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
NeOzay
wants to merge
10
commits into
EmmyLuaLs:main
Choose a base branch
from
NeOzay:fix/recursive-instance-nested-tables
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
51ad350
feat(infer): resolve nested table literals as Instance types
NeOzay e98efd5
fix(infer): address PR review feedback for Instance type narrowing
NeOzay 6d73899
fix(ci): fix clippy unwrap and reformat code
NeOzay c3cc7c6
refactor(infer): fix Instance narrowing regression and reduce nesting
NeOzay 0339b6a
fix(infer): label outer loop to resolve ambiguous break in narrow block
NeOzay 0f50901
Merge upstream/main into fix/recursive-instance-nested-tables
NeOzay 646bd23
fix(infer): guard Instance creation to optional fields only
NeOzay 0bf0265
refactor(infer): deduplicate literal_provides_optional_class_field
NeOzay d1682cc
refactor(humanize): avoid unnecessary sort for literal key lookup
NeOzay 69032e9
fix(infer): use explicit import for literal_provides_optional_class_f…
NeOzay File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -231,6 +231,16 @@ impl LuaType { | |
| matches!(self, LuaType::Unknown) | ||
| } | ||
|
|
||
| pub fn is_class_type(&self, db: &DbIndex) -> bool { | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This function probably shouldn't be here; it belongs in the specific context where you use it and should be implemented as a private function. |
||
| let type_id = match self { | ||
| LuaType::Ref(id) | LuaType::Def(id) => id, | ||
| _ => return false, | ||
| }; | ||
| db.get_type_index() | ||
| .get_type_decl(type_id) | ||
| .is_some_and(|decl| decl.is_class()) | ||
| } | ||
|
|
||
| pub fn is_nil(&self) -> bool { | ||
| matches!(self, LuaType::Nil) | ||
| } | ||
|
|
||
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why keep two type match?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, the two variants are there because the current inference intersects the declared type with the literal value (e.g. { a = 1 } → IntegerConst(1) instead of Integer).
Should accessing a provided field return the declared type or the narrowed literal constant?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The returned type must be one of these; the | here indicates you're not sure which one it is, and that shouldn't happen in tests.