Jonathan 'theJPster' Pallant
Jonathan 'theJPster' Pallant
> Run workflow? As this PR is not from an org member, one of us has to manually approve the workflow run every time - in case you submit a...
> formatting is creating lots of diffs We just test for `cargo fmt --check` so you probably just need to run `cargo fmt` locally.
> Expected — Waiting for status to be reported unfortunately it looks like adding the features to the matrix has renamed the build jobs, and so now the branch protection...
Try using 1.81. Maybe GitHub hasn't updated the image yet.
I think it still needs the SD card driver changing? And I'm still not entirely persuaded on the merits of this approach as compared to just making a different crate...
I can assure you that the maintainers are acutely aware of any annoyances to be found in our current solution. If it was easy to fix, we'd have fixed it...
Oh right, I also forgot the critical-section-single-core impl I mentioned [above](https://github.com/rust-embedded/cortex-m/issues/604#issuecomment-3070165321), which uses `no_mangle` functions, which is another reason why you cannot have two versions of cortex-m in the same...
They could but they don’t. We (the WG) do not own the PACs and co-ordinating such an update across the ecosystem would be hugely expensive in terms of effort, and...
No, I said: > would have to decide if it was going to support cortex-m 0.7 or cortex-m 0.8, because it could not do both (at least not without messy...
Yeah, maybe? That doesn't change our position on putting out breaking releases of the `cortex-m` crate.