Add new duplicate_declaration.{c,cpp} warning types
#13173
Merged
Conversation
This file contains 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
# Conflicts: # sphinx/domains/c/_symbol.py
AA-Turner
changed the title
duplicate_declaration.{c,cpp} warning types
AA-Turner
approved these changes
Jan 3, 2025
|
Thank you @julien-lecomte! A |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I have a project with many files that are similar to C syntax. Each file is compiled as if it was standalone program. For this reason, some variables are documented in what would be the equivalent of a
.cfile.However, some of those variables have the same name, but not necessarily the same purpose / documentation. For this reason, I get many warnings:
Duplicate C declaration, also defined at.I would like to neither move them to a common file, nor make their documentation the same. Meanwhile, I would also like to keep the "-W" for my CI.
My current solution was creating a logging.Filter to disable the warning, but I think that an option to
suppress_warningswould be beneficial to many users.