00:45 <re_irc> <almindor> I see there are old "unproven" feature gated "Pwm" traits in "embedded-hal v0.2.7". Is this being dropped completely for "v1.0" ?

14:36 <re_irc> <newam> almindor: I believe so, I think the problem with the ""unproven"" feature is that everyone started using them as-is and it would break a lot to change them, even though they were unproven.

15:25 <re_irc> <almindor> ok, so there are no plans for Pwm traits in embedded-hal anytime soon then

18:36 <re_irc> <chemicstry> Jan Bronicki: BSPs are quite uncommon imo. Probably because they are quite hard to write for most HAL/PACs that use singleton peripheral struct

18:37 <re_irc> <chemicstry> +in rust

18:50 <re_irc> <antoinevg> Jan Bronicki: I wouldn't necessarily _recommend_ these but this approach has worked for me so far: https://github.com/antoinevg/daisy_bsp and https://github.com/antoinevg/nucleo-h7xx

18:51 <re_irc> <antoinevg> Basically labeling pins and some very basic peripheral support.

19:47 <re_irc> <therealprof> https://github.com/nrf-rs/microbit would be another example.

20:54 <re_irc> <thejpster> github.com/rp-rs has a bunch too

21:08 <re_irc> <riskable> Is there something like "#[rustfmt::skip]" that I can pass as a little directive to rustfmt to tell it, "you don't have to put every one of these on its own line"? Like, I _want_ it to format the stuff for me I just don't want it to do this:

21:08 <re_irc> M1,

21:08 <re_irc> M3,

21:08 <re_irc> M2,

21:08 <re_irc> ... long message truncated: https://psion.agg.io/_matrix/media/r0/download/psion.agg.io/b18777ace13ff44f06edcc911b9d7ba0478cc2333be8799e5946478756cc5b76 (6 lines)