Conversation
The clang-format tools generates code that is at odds with cpplint.py. Since we run cpplint.py on every commit and (apparently) almost never run clang-format, let's simplify things by removing clang-format.
targos
left a comment
There was a problem hiding this comment.
I rarely write C++ code, but having a formatter is very useful to me for this language
Do you have an example diff? I thought that clang-format is like a stricter form of cpplint but both are supposed to adhere to the same set of rules in our C++ style guide. If they produce conflicting results, we are supposed to tweak the configs at https://github.com/nodejs/node/blob/HEAD/.clang-format and https://github.com/nodejs/node/blob/HEAD/.cpplint accordingly.
I think it would be really nice if we can run both of them. |
|
|
I see in a few places that the problem is that a line with a |
Run clang-format on the files and provide needed additional comments for the linter. Refs: nodejs#42665 (comment)
|
|
Managed to come up with a diff to make Details |
The clang-format tools generates code that is at odds with cpplint.py.
Since we run cpplint.py on every commit and (apparently) almost never
run clang-format, let's simplify things by removing clang-format.