Build with more aggressive compiler warnings
Open
- Dominant language
- C++
- Stars
- 3.1k
- Forks
- 430
- PR merge metrics
- No merged PRs in 30d
Description
My sense is we should start with enabling and fixing warnings in roughly this order:
- -Wabsolute-value
- -Wfloat-conversion
- -Wshorten-64-to-32
- -Wconversion
- -Wshadow
- -Wsign-compare
- -Wsign-conversion
Contributor guide
Research direction
Start by inspecting the repository's compiler and build configuration, then run a build with the first warning, -Wabsolute-value. Work through the listed warnings in order, and consider the issue done when the build succeeds with each warning enabled without new warnings of that class.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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