Static analysis
Open
- Dominant language
- C
- Stars
- 383
- Forks
- 215
- PR merge metrics
- No merged PRs in 30d
Description
Should we add static analysis to the CI tasks to analyse each implementation?
As it is all the exercise implementations work just fine -- according to the tests that have been written. Static analysis would add a second layer of "correctness" checking, for the current exercises and also for any exercises added into the future. So far I don't think there is any specific _need_ for this it just occurred to me that it might be a nice-to-have thing. Downsides might be potentially increased maintenance in the case of any major change to the track structure.
Thoughts?
Contributor guide
Assessment
This issue has not been assessed yet.