Changes durations in the time
module to use u64
instead of u32
#820
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Currently many time durations pass/stored throughout the HAL use nanoseconds for maximum precision. However these are stored using a
u32
for a maximum of about 4 seconds. Since delays/times longer than this could be useful and should be possible, this changes all type defs in thetime
module to useu64
instead, extending the maximum time (when stored as nanoseconds) to over 584 years.There were also several places in the HAL that import
fugit
duration types directly. These were changed to use the type defs in thetime
time module instead so that the entire HAL uses these exclusively.See the commit message for more details.
Note that the rate/frequency types defined in
time
still useu32
as rates above 4 GHz are not likely to be useful.Also note that this is a breaking change.
Checklist
#[allow]
certain lints where reasonable, but ideally justify those with a short comment.