-
Notifications
You must be signed in to change notification settings - Fork 134
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
[platform:timer] support std::chrono in Timer**::setPeriod #873
Merged
salkinium
merged 2 commits into
modm-io:develop
from
TomSaw:feature/timer-setPeriod-use-chrono
Jun 13, 2022
Merged
[platform:timer] support std::chrono in Timer**::setPeriod #873
salkinium
merged 2 commits into
modm-io:develop
from
TomSaw:feature/timer-setPeriod-use-chrono
Jun 13, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TomSaw
changed the title
[platform] support std::chrono for platform:Timer**::setPeriod()
[platform] support std::chrono for platform::Timer**::setPeriod
Jun 9, 2022
TomSaw
changed the title
[platform] support std::chrono for platform::Timer**::setPeriod
[platform] support std::chrono in platform::Timer**::setPeriod
Jun 9, 2022
TomSaw
force-pushed
the
feature/timer-setPeriod-use-chrono
branch
4 times, most recently
from
June 9, 2022 20:14
d784d0c
to
b106366
Compare
TomSaw
changed the title
[platform] support std::chrono in platform::Timer**::setPeriod
[platform:timer] support std::chrono in platform::Timer**::setPeriod
Jun 11, 2022
TomSaw
changed the title
[platform:timer] support std::chrono in platform::Timer**::setPeriod
[platform:timer] support std::chrono in Timer**::setPeriod
Jun 11, 2022
salkinium
reviewed
Jun 12, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
TomSaw
force-pushed
the
feature/timer-setPeriod-use-chrono
branch
from
June 12, 2022 11:26
b106366
to
5ddcab3
Compare
Delicious! |
Can you also check if there are examples that need to be updated? |
TomSaw
force-pushed
the
feature/timer-setPeriod-use-chrono
branch
from
June 12, 2022 14:36
c626704
to
c949daf
Compare
salkinium
approved these changes
Jun 12, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
rleh
approved these changes
Jun 12, 2022
chris-durand
approved these changes
Jun 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
+consistent use of
typename uint16_t Value
in Timer Types.+I'm not motivated to maintain the whole Timer code right now :P There's a lot / too much that may be improved,
f.e.
chrono::duration
could be provided