Enable more non-default warnings
Open
Nobody has claimed this yet.
area: buildsystem
improvement
to-discuss
- Dominant language
- Python
- Stars
- 14.4k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
Although we've long hat -Wall and -Wextra, there is more useful warnings:
https://kristerw.blogspot.de/2017/09/useful-gcc-warning-options-not-enabled.html
Which of those should we activate?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the linked GCC warning-options article and locate the project's compiler-warning configuration. Evaluate candidate warnings against the existing -Wall and -Wextra build, including supported configurations. Done means agreeing on suitable additional warnings and enabling them without breaking the build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- build-system, compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100