Finomnis
Finomnis
@jamesmunns I'm not entirely sure why the CI doesn't run, might be setting in the repository?
@jamesmunns Also you mentioned that this crate is not really maintained; if you want I can become a co-maintainer. Although I don't think there will be much activity after this.
> @Finomnis added you as a collaborator and invited you as a crate owner. Please feel free to make a 0.3/1.0 release. Cool! Thanks. I'll try my best to serve...
Still nothing? What's the showstopper, is the backport complexity bigger than expected? Are code changes required, or open issues? I am willed to assist if I can.
I'd also love [`embedded-graphics`](https://docs.rs/embedded-graphics/latest/embedded_graphics/) compatibility. That'd be so cool. Shouldn't be too hard to accomplish, from my first impressions. **EDIT:** Never mind, I think it's quite a bit harder than...
@AaronErhardt Why is `next-release-devel` 102 commits behind master? What's the current workflow right now?
> From what I see, most of the `std::` uses could simply be changed to `core::`. Not sure about the places where a `Vec` is used, but that might be...
Clashes with #874. Also only tests the `tim2` peripheral; as many of the macros are hand-synced code duplication, it would make much sense to test all the timers.
Still interested in thoughts :)
Here is a sketchup of what I kind of had in mind: ```rust // Macro generated user code, like // gpt1_mono!(1_000_000); // Could then also be used to generate the...