Open thejpster opened 4 years ago
I think something that should be done on the next breaking release is using the "sealed trait" pattern for *Pin
traits.
I.e. having a private trait Sealed
and requiring *Pin: Sealed
. This would be better than (and should be done instead of) writing "DO NOT IMPLEMENT THIS TRAIT" in the docs.
Btw, why are internal macros such as uart_hal_macro
and uart_pin_macro
exposed in the API ?
Happy to see a PR.
Macros I think are shared between tm4c123 and 129 and hence exported from tm4c common.
What do we need to do to put out a 1.0 release? One assumes we at least need an embedded-hal 1.0 (https://github.com/rust-embedded/embedded-hal/issues/177)