Skip to content
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

Apply clang-tidy fixes #114

Merged
merged 5 commits into from Aug 26, 2019
Merged

Conversation

rhaschke
Copy link
Contributor

@rhaschke rhaschke commented Aug 8, 2019

Apply the most important clang-tidy fixes. I just dropped the naming conventions of MoveIt, because they are not followed in this rep.

Copy link
Contributor

@BryceStevenWilley BryceStevenWilley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just fixing auto in loops.

However, I don't think this will fix ros-planning/moveit#1607 (comment), if that's what it's intended for. I think that's a missing override in shapes. If not, carry on. :)

@@ -145,9 +145,9 @@ void bodies::computeBoundingSphere(const std::vector<const bodies::Body*>& bodie

// TODO - expand to all body types
unsigned int vertex_count = 0;
for (unsigned int i = 0; i < bodies.size(); i++)
for (auto body : bodies)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should fix auto in loops.

@rhaschke
Copy link
Contributor Author

rhaschke commented Aug 8, 2019

However, I don't think this will fix ros-planning/moveit#1607 (comment), if that's what it's intended for.

That's true. Due to its urgency, I fixed the mentioned issue directly via #113.

@rhaschke rhaschke merged commit e110550 into ros-planning:melodic-devel Aug 26, 2019
@rhaschke rhaschke deleted the clang-tidy branch August 26, 2019 13:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants