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

Create a separate Steady Time datatype instead of having it embedded as an enumeration of time types #643

Open
tfoote opened this issue May 5, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@tfoote
Copy link
Contributor

tfoote commented May 5, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant