Consider using `std::chrono` for compile time type safety. Define a custom clock domain using something like `std::chrono::time_point<deviceio_monothonic_clock>` and a custom `deviceio_monothonic_clock` that would use platform specific query mechanisms.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 385
- Forks
- 88
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 82
Description
Consider using std::chrono for compile time type safety. Define a custom clock domain using something like std::chrono::time_point<deviceio_monothonic_clock> and a custom deviceio_monothonic_clock that would use platform specific query mechanisms.
Originally posted by @aristarkhovNV in https://github.com/NVIDIA/IsaacTeleop/pull/352#discussion_r3041742201
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the originating discussion in PR #352 and determine how the proposed std::chrono time_point and custom deviceio_monothonic_clock would fit the project. Review the platform-specific query mechanisms mentioned in the issue; the work is done when clock values have compile-time type safety across those mechanisms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- robotics
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100