Code formatting

[eldruin]

No description provided.

[rust-highfive]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @thejpster (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

[thejpster]

Looks good, but I wonder if we should enforce this in CI to avoid subsequent PRs diverging from the rustfmt standard.

[eldruin]

@thejpster Sure thing. I added the check now.

[therealprof]

We're planning to use more GitHub Actions for CI and these kind of checks. Maybe it would make more sense to go straight to GHA instead of using Travis for a short bit?

Adding it should be as simple as copying these two workflows: https://github.com/rust-embedded/svd2rust/tree/master/.github/workflows

[therealprof]

Well, wrong example. The CI workflow is the wrong one. ;) This should hit the spot better: https://github.com/stm32-rs/stm32f1xx-hal/blob/master/.github/workflows/rustfmt.yml

[eldruin]

@therealprof Sure. GHA are quite nice. I added only the formatting check for now. Building CI could be done in a separate PR.

[therealprof]

LGTM, thanks.

[therealprof]

bors r+

[therealprof]

Hm, bors crashed on this. Let's try again.

bors merge

[eldruin]

@therealprof bors has been having a couple rough days. Could you try again?

[korken89]

bors retry

[korken89]

bors cancel

[korken89]

bors r+

[adamgreig]

Thanks for the PR, and sorry bors never quite managed to merge it... we've now moved this crate to the cortex-m repository. We could consider adding rustfmt over there to the whole repository, but I'm closing the PR here.