Clock class about rclpy HOT 4 CLOSED

I'm not sure it would make sense to implement the Clock class without the jump support. Otherwise users won't be able to know that time has skipped when the clock has changed. The class is trivial enough that the jump API and ability to pump it from a time source are important for confirming that the API is set that I'd rather not try to review just the simpler API/structure before the higher level functions are confirmed to work.

The timer should have a clock associated with it to test for how long has elapsed. It's ticketed in rclcpp here: ros2/rclcpp#465

from rclpy.

I see. I don’t feel comfortable I can have it implemented in reasonable time. I will pass on this ticket.

What’s the right process? Just close this issue? Your original ticket still has all the tasks.

from rclpy.

Since we have the other ticket with the tracking info we could close this out. If you do find some time in the future this could be a good place to come back to. You could also start the implementation of the clock, but we just wouldn't plan to merge it until the other parts were implemented.

from rclpy.

Thanks!

from rclpy.