-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prefer empty()
over size()
when checking container state
#3033
Prefer empty()
over size()
when checking container state
#3033
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be possible to perform a find-replace to change from empty()
to empty ()
. Because as it is, we are accepting a PR that breaks PCL's coding style with every change it introduced :/
Well if I replace all Btw: This is the part of the coding style that I really don't like at all. I don't have an idea until now, which benefit we got by a whitespace before a bracket (for me it decreases readability). |
Ups wrong button, didnt' wanted to close this PR xD |
Yes, this whitespace was a notorious choice for the style guide. (Not made by any of us who are currently active in PCL.) I think when we finally adopt automatic code formatting tools we can change it. But we have to live with it, at least for now. |
…adability-container-size-empty' -fix
3b06eb0
to
67c1263
Compare
Thank you for the sanity check ^^ Once we get the formatting tool running on CI I'm open to discuss changes to the style guide. |
empty()
over size()
when checking container state
Changes are done by
run-clang-tidy -header-filter='.*' -checks='-*,readability-container-size-empty' -fix