change order of imports (work around rust-analyzer bug?)

I can't figure out why rust-analyzer on my system isn't work
correctly but if I change the order of imports things work better.

If this breaks things for Foundation Devices (@eupn) let me know,
I will poke at this some more and try to figure it out. In theory
it should have no impact but somehow I'm getting the atsamd target
*always* live in my vscode environment, even when it is switched
off when it isn't the last target in the list (and this overrides
all of the rust-analyzer settings for other targets).
This commit is contained in:
bunnie 2024-01-21 01:10:46 +08:00
parent 7db25efcd5
commit 002a621181

View file

@ -29,13 +29,6 @@ mod precursor_pvt;
#[rustfmt::skip]
pub use precursor_pvt::*;
#[cfg(feature = "atsama5d27")]
#[rustfmt::skip]
mod atsama5d27;
#[cfg(feature = "atsama5d27")]
#[rustfmt::skip]
pub use atsama5d27::*;
#[cfg(feature = "cramium-soc")]
#[rustfmt::skip]
mod cramium_soc;
@ -50,6 +43,13 @@ mod cramium_fpga;
#[rustfmt::skip]
pub use cramium_fpga::*;
#[cfg(feature = "atsama5d27")]
#[rustfmt::skip]
mod atsama5d27;
#[cfg(feature = "atsama5d27")]
#[rustfmt::skip]
pub use atsama5d27::*;
// Hosted mode includes nothing, as it relies on the abstract host
// architecture for I/O; so this file is empty when the "hosted"
// configuration is selected and there are no corresponding "hosted"