Peter Taylor

I would also like to see this abstraction. The `Duration` struct from time.rs is now (as of 0.2.10) usable in embedded contexts. I would like to have an architecture/device agnostic...

What I've been currently pursuing is an Instant struct with a `nanoseconds: i64` field and a const Ratio to where the the tick count (from my underlying counter/timer) * the...

I've put my current effort up here: [embedded-time](https://github.com/PTaylor-FluenTech/embedded-time). Comments, suggestions, and PRs are welcome.

> I've put my current effort up here: [embedded-time](https://github.com/PTaylor-FluenTech/embedded-time). Comments, suggestions, and PRs are welcome. I've looked at several approaches including const generics and others. At the moment my [ratiometric](https://github.com/PTaylor-FluenTech/embedded-time/tree/ratiometric)...

The [`embedded-time`](https://github.com/FluenTech/embedded-time) crate provides a `Clock` trait to abstract hardware timers/counters. It currently includes a blocking `delay()` function as well as the ability to get a duration elapsed since some...

@arjanmels Actually, `embedded-time` does not currently have any way to execute a task upon the expiration of a timer. It's something I tried to implement, but put it on hold...

I don't see much use for the `CountDown` trait in its current form. I think it needs a fair bit of attention.

> Additionally, choosing a Time type seems difficult because of precision and conversion issues. I have released (and continue to develop) `embedded-time` (#211) aimed at allowing use of Time-type values...

> I see only duration types. What about frequencies and baudrates? @burrbull There is a `Period` type that is an `i32` `rational::Ratio`. I use it in the durations to specify...

@burrbull Initial frequency-type functionality has been added in v0.5.0