-
Notifications
You must be signed in to change notification settings - Fork 1
andyz/squashed_improvements branch, merged w/master, clang tests fixed
#63
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
Merged
AndyZe
merged 16 commits into
PickNikRobotics:andyz/squashed_improvements
from
zultron:zultron/andyz/squashed_improvements_merged
Sep 20, 2020
Merged
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
518206d
Clang tidy fixes (#53)
nbbrooks 29b975b
Clean up inline functions (#54)
nbbrooks 250aa4b
Update executable names in Readme (#56)
91fdaf7
Merge remote-tracking branch 'origin/master' into andyz/squashed_impr…
zultron 962197d
Run `clang-format`
zultron e12fb23
Adjust clang-format rules and re-run
zultron daad03d
single_joint_generator: Silence compiler warning
zultron 9bdf11c
single_joint_generator: Silence compiler warning
zultron e92bb92
test/trajectory_generation_test: Silence compiler warning
zultron 9bbf67d
Remove junk files
zultron b3cfcbf
.gitignore generated `.catkin-tools` directory
zultron f48cf32
Change `int` to `size_t` for vector indices in tests
zultron 159318f
trajectory_generator.cpp: Fix `clang-tidy` errors
zultron f9fd220
single_joint_generator.cpp: Fix clang-tidy errors
zultron 58fc12a
Slence clang-tidy warnings
zultron a40551f
Silence clang-tidy warnings
zultron File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Empty file.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
Empty file.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -18,4 +18,8 @@ | |
| .DS_Store | ||
|
|
||
| # SSH Keys (used for Docker) | ||
| id_rsa | ||
| id_rsa | ||
|
|
||
| # Catkin tools | ||
| /.catkin-tools/ | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 can't remember what style guide we're using for this project. The Google style guide says this should be kNoError:
https://google.github.io/styleguide/cppguide.html#Enumerator_Names
@nbbrooks is it cool if we specify Google style for this repo?
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 think it makes sense to use Google style because we are using Google clang format
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.
Related PR that should either be closed or merged: #60
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'm not arguing for a naming convention this way or that, but those changes were introduced in #53, and made their way into this PR with the merge from
masterbranch. See here:https://github.com/PickNikRobotics/trackjoint/pull/53/files#diff-c036aecfa9831ff50f1e589083907289
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.
OK. We must be using the ROS style guide then. Would you mind reviewing/merging this PR so that will be documented in the README?
#60
ROS style guide: http://wiki.ros.org/CppStyleGuide
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.
ugh, should have reviewed this a while ago