diff options
| author | perlindgren <per.lindgren@ltu.se> | 2021-12-21 19:49:09 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-12-21 19:49:09 +0100 |
| commit | d3d650b2c7e8492c96d8a37d85620ff491178632 (patch) | |
| tree | 6e8452022ef875c7c002161fe5cf3250b31e045e /book/en | |
| parent | 278207e2ec02b00e8719d983f499e202276e3359 (diff) | |
Update tips_monotonic_impl.md
text polishing
Diffstat (limited to 'book/en')
| -rw-r--r-- | book/en/src/by-example/tips_monotonic_impl.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/book/en/src/by-example/tips_monotonic_impl.md b/book/en/src/by-example/tips_monotonic_impl.md index 99e155d..24df771 100644 --- a/book/en/src/by-example/tips_monotonic_impl.md +++ b/book/en/src/by-example/tips_monotonic_impl.md @@ -9,7 +9,7 @@ Implementing time counting that supports large time spans is generally **difficu implementing time handling was a common problem. Moreover, the relation between time and timers used for scheduling was difficult to understand. -For RTIC 0.6 we have moved to assume the user has a time library, e.g. [`fugit`] or [`embedded_time`], +For RTIC 0.6 we instead assume the user has a time library, e.g. [`fugit`] or [`embedded_time`], as the basis for all time-based operations when implementing `Monotonic`. This makes it almost trivial to implement the `Monotonic` trait allowing the use of any timer in the system for scheduling. |