Conversation
Signed-off-by: Shane Loretz <sloretz@osrfoundation.org>
clalancette
left a comment
There was a problem hiding this comment.
Seems reasonable to me with green CI (though I think we should run tests with --packages-above rclcpp, just to make sure no downstream packages have a problem with this).
What might happen downstream at run time that needs to be tested? |
Actually, that's a good point. I missed that the build was |
Signed-off-by: Shane Loretz <sloretz@osrfoundation.org> Signed-off-by: Shane Loretz <sloretz@osrfoundation.org>
Signed-off-by: Shane Loretz <sloretz@osrfoundation.org> Signed-off-by: Shane Loretz <sloretz@osrfoundation.org>
Signed-off-by: Shane Loretz <sloretz@osrfoundation.org> Signed-off-by: Shane Loretz <sloretz@osrfoundation.org>
Signed-off-by: Shane Loretz <sloretz@osrfoundation.org> Signed-off-by: Shane Loretz <sloretz@osrfoundation.org>
|
Can this be backported to humble? Would save me a workaround: https://github.com/nobleo/ros2_fmt_logger/blob/14e0cb5e0407e33aaecf88787296208b896a7f17/include/ros2_fmt_logger/ros2_fmt_logger.hpp#L572..L574 |
|
this is ABI breaking change. application compiled against the old version would expect the non-const signature, so i think this would break the user space. i do not think we can backport this? |
|
Ah, then nevermind. I'll just wait for the EOL 😄 |
I think
now()can be marked asconst. All it does is call rcl_clock_get_now() which doesn't look like it modifies the clock to me.get_nowisrcl_get_ros_time: https://github.com/ros2/rcl/blob/e4f7e1367dfda83d3e309397f9201642ebe38618/rcl/src/rcl/time.c#L65-L73get_nowisrcl_get_system_time: https://github.com/ros2/rcl/blob/e4f7e1367dfda83d3e309397f9201642ebe38618/rcl/src/rcl/time.c#L44-L48get_nowisrcl_get_steady_time: https://github.com/ros2/rcl/blob/e4f7e1367dfda83d3e309397f9201642ebe38618/rcl/src/rcl/time.c#L36-L40