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

FT #36 - Redefine c_time to not be silly #39

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rickyelopez
Copy link
Member

@rickyelopez rickyelopez commented Oct 10, 2020

c_time now reports the value of systick_uptime_millis, which means we
should never need to update c_time any more! It should always contain
the most up to date value. This will probably have little to no actual
impact, but in theory it means that all our timing operations should be
much faster.
addresses #36
NOTE: this needs validation!

c_time now reports the value of systick_uptime_millis, which means we
should _never_ need to update c_time any more! It should always contain
the most up to date value. This will probably have little to no actual
impact, but in theory it means that all our timing operations should be
much faster.
addresses #36
NOTE: this needs validation!
@rickyelopez rickyelopez marked this pull request as draft October 10, 2020 21:21
@rickyelopez rickyelopez self-assigned this Oct 10, 2020
@rickyelopez rickyelopez added the enhancement New feature or request label Oct 10, 2020
@rickyelopez rickyelopez changed the title Redefine c_time to not be silly FT #36 - Redefine c_time to not be silly Oct 10, 2020
@rickyelopez rickyelopez linked an issue Oct 10, 2020 that may be closed by this pull request
3 tasks
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

Successfully merging this pull request may close these issues.

redefine c_time so it doesn't use millis()
1 participant