-
Notifications
You must be signed in to change notification settings - Fork 50
update #845
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
base: main
Are you sure you want to change the base?
update #845
Conversation
Summary of ChangesHello @xuhuanzy, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces a fix that refines the type checking mechanism within the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
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.
Code Review
This pull request appears to fix an issue with recursive type aliases, and also makes array index type checking configurable. However, I've found a potential issue in the implementation of the type alias fix.
The change in fast_eq_check seems to incorrectly equate a nullable type T? with a non-nullable type T. This could hide potential nil-related bugs. Additionally, the new configuration for array index checking seems to have inverted logic, causing issues with the default settings. Please see my detailed comments.
crates/emmylua_code_analysis/src/semantic/type_check/complex_type/array_type_check.rs
Show resolved
Hide resolved
```lua fun<T>(a: T): T ```
No description provided.