You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Steady Time is a fundamentally different type than ROS Time and giving it it's own type will allow us to leverage compile time checking of the datatype instead of runtime. For steady time it can also contain logic to compare and verify the epoch ID for any other steady time to make sure you're comparing across the same epoch.
There's a related issue to create a message to represent it as well: ros2/rcl_interfaces#104
This has been discussed during development and was flagged during the API review for followup. ros2/common_interfaces#86
The text was updated successfully, but these errors were encountered:
Steady Time is a fundamentally different type than ROS Time and giving it it's own type will allow us to leverage compile time checking of the datatype instead of runtime. For steady time it can also contain logic to compare and verify the epoch ID for any other steady time to make sure you're comparing across the same epoch.
There's a related issue to create a message to represent it as well: ros2/rcl_interfaces#104
This has been discussed during development and was flagged during the API review for followup. ros2/common_interfaces#86
The text was updated successfully, but these errors were encountered: