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

support unique_ptr. #1771

Merged
merged 2 commits into from
Nov 24, 2019
Merged

support unique_ptr. #1771

merged 2 commits into from
Nov 24, 2019

Conversation

v4hn
Copy link
Contributor

@v4hn v4hn commented Nov 24, 2019

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 .

@v4hn v4hn requested a review from mlautman as a code owner November 24, 2019 11:03
@v4hn v4hn requested a review from rhaschke November 24, 2019 11:04
@rhaschke rhaschke merged commit 64663d9 into master Nov 24, 2019
@rhaschke rhaschke deleted the pr-master-unique-ptr branch November 24, 2019 12:16
@rhaschke
Copy link
Contributor

I started to implement UniquePtrs as well. Merged. Next I will address the (unrelated) Travis issue.

rhaschke pushed a commit that referenced this pull request Nov 24, 2019
rhaschke pushed a commit to ubi-agni/moveit that referenced this pull request Nov 24, 2019
@v4hn
Copy link
Contributor Author

v4hn commented Nov 24, 2019

Next I will address the (unrelated) Travis issue.

If I see this correctly, you introduced it with a direct push to the master branch and you force-pushed to address it?

rhaschke pushed a commit that referenced this pull request Nov 24, 2019
@rhaschke
Copy link
Contributor

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:

@v4hn
Copy link
Contributor Author

v4hn commented Nov 25, 2019 via email

sjahr added a commit to sjahr/moveit that referenced this pull request Jun 21, 2024
…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>
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.

add *UniquePtr to definition macro
2 participants