Problem
The current clang-tidy run on the existing codebase produces 100+ warnings.
Existing code that does not satisfy clang-tidy is mixed with newer upcoming PRs that use the clang-tidy style of writing, making the code more confusing to read.
One example is the ramcoretests.cxx; original test cases are written in one style, and the newer test cases are written in clang-tidy style.
Proposal
These are pre-existing and unrelated to any recent changes, but I propose that they be addressed to make future development easier.
Problem
The current
clang-tidyrun on the existing codebase produces 100+ warnings.Existing code that does not satisfy
clang-tidyis mixed with newer upcoming PRs that use theclang-tidystyle of writing, making the code more confusing to read.One example is the
ramcoretests.cxx; original test cases are written in one style, and the newer test cases are written inclang-tidystyle.Proposal
These are pre-existing and unrelated to any recent changes, but I propose that they be addressed to make future development easier.