-
Notifications
You must be signed in to change notification settings - Fork 43
fix(lint): Suppress latest clang-tidy warnings #361
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
Summary of ChangesHello @junrushao, 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 recently introduced Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. 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 correctly suppresses a clang-tidy warning (bugprone-unchecked-optional-access). The unchecked access to the std::optional value is safe in this context, as the calling function TryCall ensures through TrySetAux that all optionals in the tuple have a value before CallAux is invoked. This is a good cleanup to reduce static analysis noise. I've also included a suggestion to use std::forward for more idiomatic C++, which simplifies the argument forwarding logic.
| // NOLINTNEXTLINE(bugprone-unchecked-optional-access) | ||
| return f_(static_cast<std::tuple_element_t<I, PackedArgs>>(std::move(*std::get<I>(tuple)))...); |
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 argument forwarding logic can be simplified and made more idiomatic by using std::forward. It achieves the same goal of correctly forwarding the value category of the arguments to the wrapped function f_ but is more concise and recognizable as a forwarding pattern.
// NOLINTNEXTLINE(bugprone-unchecked-optional-access)
return f_(std::forward<std::tuple_element_t<I, PackedArgs>>(*std::get<I>(tuple))...);
Ubospica
left a comment
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.
LGTM!
Introduced by #286, where
CaptureTuple, i.e.CaptureTupleAux<PackedArgs>::type, is defined as:and star access to its
std::optionalis indeed unchecked but intended.