-
Notifications
You must be signed in to change notification settings - Fork 102
chore: Move deprecated annotations to fix a Clippy warning #391
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
Conversation
Signed-off-by: Chris Hennick <4961925+Pr0methean@users.noreply.github.com>
|
⏳ I'm reviewing this pull request for security vulnerabilities and code quality issues. I'll provide an update when I'm done |
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.
Summary of Changes
Hello @Pr0methean, 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 addresses a Clippy warning by relocating #[deprecated] attributes in src/types.rs. Specifically, the attributes are moved from individual try_from methods to their respective impl blocks, resolving the useless_deprecated lint and improving code clarity regarding deprecation.
Highlights
- Deprecation Annotation Relocation: The #[deprecated] attributes for TryFrom implementations related to DateTime and OffsetDateTime have been moved from the try_from methods to the impl blocks themselves.
- Clippy Warning Resolution: This change specifically resolves a useless_deprecated Clippy warning, ensuring better adherence to Rust's linting practices.
- Code Cleanliness: The #[allow(useless_deprecated)] attributes, which were previously used to suppress the warning, have been removed, leading to cleaner code.
Using Gemini Code Assist
The 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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.
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
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
|
✅ I finished the code review, and didn't find any security or code quality issues. |
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 addresses a clippy::useless_deprecated warning by moving the #[deprecated] attributes from the try_from methods to their containing impl blocks. This is the correct way to deprecate a trait implementation in Rust. The change is correct and improves code maintainability. I have no further suggestions.
Signed-off-by: Chris Hennick <4961925+Pr0methean@users.noreply.github.com>
* chore: Move deprecated annotations to fix a Clippy warning Signed-off-by: Chris Hennick <4961925+Pr0methean@users.noreply.github.com> * chore: Remove the annotations, since moving them doesn't fix the error Signed-off-by: Chris Hennick <4961925+Pr0methean@users.noreply.github.com> --------- Signed-off-by: Chris Hennick <4961925+Pr0methean@users.noreply.github.com>
No description provided.