-
Notifications
You must be signed in to change notification settings - Fork 525
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
Fix clang-tidy issues #1706
Fix clang-tidy issues #1706
Conversation
I think I got most of them. I'm still seeing some "candidate function not viable: no known conversion ..." errors locally, will look into it tomorrow. |
Codecov ReportBase: 50.97% // Head: 50.98% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #1706 +/- ##
==========================================
+ Coverage 50.97% 50.98% +0.01%
==========================================
Files 378 378
Lines 31649 31657 +8
==========================================
+ Hits 16131 16137 +6
- Misses 15518 15520 +2
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
This pull request is in conflict. Could you fix it @rhaschke? |
With the last commit, clang-tidy succeeds for me locally |
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.
Thanks for handling this, Hennig. There are a few clang warnings left though (which cannot be resolved automatically).
What warnings are you talking about? CI is happy and locally I don't see related warnings or errors anymore either? |
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.
I don't see any warnings locally, either.
CI doesn't use |
I approve as well. The warnings can be tackled later as well. This PR should be merged soon to unblock other PRs (which currently will fail due to clang-tidy issues). |
* Blindly apply automatic clang-tidy fixes * Exemplarily cleanup a few automatic clang-tidy fixes * Clang-tidy fixups * Missed const-ref fixups * Fix unsupported non-const -> const * More fixes Co-authored-by: Henning Kayser <henningkayser@picknik.ai> (cherry picked from commit 132ad28) # Conflicts: # moveit_ros/moveit_servo/include/moveit_servo/utilities.h # moveit_ros/moveit_servo/src/utilities.cpp # moveit_ros/planning/moveit_cpp/include/moveit/moveit_cpp/plan_solutions.hpp # moveit_ros/planning/moveit_cpp/include/moveit/moveit_cpp/planning_component.h # moveit_ros/planning/moveit_cpp/src/planning_component.cpp
* Blindly apply automatic clang-tidy fixes * Cleanup wrong fixes * Missed const-ref fixups * Fix unsupported non-const -> const * More fixes Co-authored-by: Henning Kayser <henningkayser@picknik.ai>
Having the clang-tidy check
performance-unnecessary-value-param
disabled for a few years, lead to the introduction of several shortcomings in the code, which should be fixed asap.Applying all automatic fixes from clang-tidy is not a good idea as you can see from second commit, trying to cleanup a few of them. Somebody from the MoveIt2 team should take over and clean up the remaining ones. @henningkayser, can you please coordinate this work?