-
Notifications
You must be signed in to change notification settings - Fork 90
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
update signature for added pub/sub options #46
Conversation
Signed-off-by: Erik Boasson <eb@ilities.com>
I would suggest holding off on branch and get ros2/rmw#188 (comment) resolved first. Than you should be easily able to keep supporting both ROS distros from the same branch. |
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.
Looks right to me.
I wasn't able to find a solution with type reflection or SFINAE to make it cross-compatible, but I think I found a decent enough alternative using #ifdefs: |
I figured out how to do this cleanly with SFINAE! I prefer this approach, but I'll leave you guys to choose. A few tricks:
|
@rotu, on macOS it breaks 😞 ... but now there is ros2/rmw#188 and that's a clean solution. |
Good to know. What’s the failure on MacOS? |
I get this:
And checking the contents of the library with
|
Closing because #51 sorted it out |
This relates to ros2/rmw#187.
Before merging, it'd probably be best to make a "dashing" branch.
Signed-off-by: Erik Boasson eb@ilities.com