Fix performance-faster-string-find
warning reported by clang-tidy
#1102
Labels
performance-faster-string-find
warning reported by clang-tidy
#1102
Search before asking
Motivation
This issue is tracked by #1029.
We welcome new contributors to take these issues as a beginning of a deep dive to kvrocks
Currently we have enabled lots of clang-tidy checks, but there are so many reports already exist in the kvrocks code, so we cannot treat these report as errors to block future PR with some clang-tidy reported warnings in CI.
Hence the goal of this issue is to solve all
performance-faster-string-find
tagged clang-tidy reports, and then enablewarnings-as-errors
for this specific check in.clang-tidy
.To get clang-tidy reports for latest kvrocks code, there are several ways: you can run
./x.py check tidy
locally, or check the log of the latest run of GitHub Actions on the unstable branch (e.g. https://github.com/apache/incubator-kvrocks/actions/runs/3449328741/jobs/5757148924#step:8:916). To be friendly for new contributors, we list allperformance-faster-string-find
tagged reports below, so in normal cases you can just follow the log below and fix them one by one.Some of these reports will give modification suggestions in the log, you can refer to them directly; otherwise, you need to understand the content of the warning and combine your C++ knowledge to fix it. (Fortunately, most reports (except those by clang static analyzer) are intuitive and easy to fix.)
When you fixed these all reports listed above, you can now add the check
performance-faster-string-find
towarnings-as-errors
in.clang-tidy
(in the root dir of the repo): We show a sample diff below to illustrate how to modify.clang-tidy
:Then, if all of the above are completed, congratulations, you can submit a PR for your changes now!
Solution
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: