PragmaTwice opened a new issue, #800: URL: https://github.com/apache/incubator-kvrocks/issues/800
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/incubator-kvrocks/issues) and found no similar issues. ### Motivation clang-tidy is described in #602. clang-format is currently the de facto standard of C++ code formatting. It has lots of benefits, like: - currently, cpplint reports some format error, but it can hardly automatically fix the code. So we need check errors in CI, and manually fix them one by one. But in clang-format, we can format code to a consistent style with just one command. And we can even add the auto-fix phase to CI (lots of projects do so). That is a huge convenience for developers. - We cannot control the version of cpplint well: it has different report in different version for same code. - It cannot handle some detail of C++ language well. clang-format uses Clang AST and every powerful compiler technology in Clang. C++ is a super complicated language, no one can handle the syntax and semantics in different C++ standard well, except compilers like GCC or Clang. It is the core reason why cpplint and cppcheck failed to become great tools (recently cppcheck support to use libClang instead of its own toy parser and type/semantics checker). ### Solution _No response_ ### Are you willing to submit a PR? - [ ] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
