-
Notifications
You must be signed in to change notification settings - Fork 139
Avoid defined but not used warning in yyjson.c
#498
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
bryceschober
commented
Sep 12, 2025
``` ./src/yyjson.c:4308:18: warning: ‘f64_pow10_table’ defined but not used [-Wunused-const-variable=] 4308 | static const f64 f64_pow10_table[] = { | ^~~~~~~~~~~~~~~ ```
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 @bryceschober, 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 resolves a specific compiler warning in 'src/yyjson.c' where the 'f64_pow10_table' was being defined but not used under certain compilation configurations. The change conditionally compiles this table, ensuring it is only included when the 'YYJSON_DOUBLE_MATH_CORRECT' macro is active, thus eliminating the warning without impacting the library's functionality.
Highlights
- Compiler Warning Resolution: Addressed a 'defined but not used' compiler warning for the 'f64_pow10_table' in 'src/yyjson.c'.
- Conditional Compilation: Implemented conditional compilation for 'f64_pow10_table' using '#if YYJSON_DOUBLE_MATH_CORRECT' to ensure it is only defined when actively used.
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. ↩
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 addresses the 'defined but not used' warning for f64_pow10_table
by wrapping its definition in the YYJSON_DOUBLE_MATH_CORRECT
preprocessor directive. The fix is appropriate as the table is only used when this macro is enabled. I have one minor suggestion for further improvement to enhance code organization.
@@ -4305,9 +4305,11 @@ static_inline u64 diy_fp_to_ieee_raw(diy_fp fp) { | |||
#define F64_POW10_EXP_MAX_EXACT 22 | |||
|
|||
/** Cached pow10 table. */ | |||
#if YYJSON_DOUBLE_MATH_CORRECT |
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.