Fix code formatting + check it on bors

[eldruin]

This was missed in #246.

[rust-highfive]

r? @ryankurte

(rust-highfive has picked a reviewer for you, use r? to override)

[eldruin]

bors try

[therealprof]

LGTM, thanks.

bors r+

[eldruin]

bors r=therealprof

[bors]

Already running a review

[bors]

Timed out.

[bors]

try

Timed out.

[eldruin]

bors r=therealprof

[bors]

Canceled.

[eldruin]

bors try

[eldruin]

bors try

[bors]

try

Already running a review

[eldruin]

bors try

[bors]

try

Already running a review

[eldruin]

Sorry for the back and forth. The bors requirements were not right.
Could you review this again @therealprof?

[bors]

try

Timed out.

[therealprof]

Sure.

bors r+

[bors]

Build succeeded:

• ci-linux (1.35.0, x86_64-unknown-linux-gnu)
• ci-linux (stable, thumbv6m-none-eabi)
• ci-linux (stable, thumbv7m-none-eabi)
• ci-linux (stable, x86_64-unknown-linux-gnu)
• fmt

[therealprof]

Just for reference: I'm not super keen on the idea of making formatting checks mandatory. We had problems in the past when formatting rules changed (similar to clippy rules) and we should actually run CI on a schedule and not just on PRs (which should be fine since they should be up-to-date re formatting).

Here's to hope that Rust is not going to make a lot of tweaks to the formatting to not get back at us. 😅 Let's see how it goes.

[eldruin]

True. clippy bit me all over the place with a rule I believe is not good and I am still not even done updating all my drivers to disregard it. fmt has been quite stable so far, but yeah, good point.