-
Notifications
You must be signed in to change notification settings - Fork 938
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
support unique_ptr. #1771
support unique_ptr. #1771
Conversation
I started to implement UniquePtrs as well. Merged. Next I will address the (unrelated) Travis issue. |
If I see this correctly, you introduced it with a direct push to the |
Yes, I cleaned up the recent history (since yesterday) of both master and melodic-devel branches |
Yes, I cleaned up the recent history (since yesterday) of both master and melodic-devel branches
to have the very same commits on both branches for the following PRs:
I do understand your motivation, but force-pushing the main branches is bad nonetheless.
|
…oveit#1771) * Add a version of computeTimeStamps() to yield a fixed num. waypoints * Add unit test * Prevent an ambiguous function signature * Remove debugging stuff * Can't have fewer than 2 waypoints * Warning about sparse waypoint spacing * Doxygen comments * Clarify about changing the shape of the path * Better comment Co-authored-by: Sebastian Jahr <sebastian.jahr@tuta.io> Co-authored-by: Sebastian Jahr <sebastian.jahr@tuta.io>
Lately, we encountered a number of interfaces, where unique_ptr
would be the preferred smart pointer to use.
This adds them to the class forward macros.
Fixes #1770 .