Enable warnings in our C code
Open
- Dominant language
- Haskell
- Stars
- 301
- Forks
- 144
- Avg merge
- 7d 22h
- Merged PRs (30d)
- 1
Description
For example [this problem](https://github.com/haskell/bytestring/pull/582#issuecomment-1522476846) with a recent patch would have been trivial to diagnose if we enabled `-Wconversion`. But enabling a reasonable warning set would cause a lot of noise from our existing C code, so this task has rather low priority.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files or tests; start by locating the build configuration and C sources used by bytestring, then inspect the effect of -Wconversion and other reasonable warnings. Done means the warning set is enabled without overwhelming noise from existing C code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100