From 002a621181759fd39d241022f2b8a723bd9c6a73 Mon Sep 17 00:00:00 2001 From: bunnie Date: Sun, 21 Jan 2024 01:10:46 +0800 Subject: [PATCH] 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). --- utralib/src/generated.rs | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/utralib/src/generated.rs b/utralib/src/generated.rs index da757c011..c8b08a2a2 100644 --- a/utralib/src/generated.rs +++ b/utralib/src/generated.rs @@ -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"