Use unstable rustfmt features to ensure import style #5065

Activity

1. rami3l

   self-assigned this

   on Sep 8, 2026
2. rami3l

   added

   enhancement

   on Sep 8, 2026
3. rami3l commented on Sep 9, 2026

   

   rami3l

   on Sep 9, 2026

   Last edited by rami3l

   MemberAuthor

   More actions

   group_imports = "StdExternalCrate"
   imports_granularity = "Crate"

   Yes, these have been very stable IME.

   (I don't think you need unstable_features if you run nightly with these?)

   Originally posted by @djc in #5064 (comment)

   According to the docs:

   To enable unstable options, set unstable_features = true in rustfmt.toml or pass --unstable-features to rustfmt.

   So this looks like the semantics was about to change in rust-lang/rustfmt#4353 (comment) but the migration never landed.

   OTOH to facilitate use in IDEs so that we can never worry about reorganizing imports, I'm discovering the feasibility of adding a recommended rust-analyzer config that looks like so:

   rustfmt = { extraArgs = { "+nightly", "--config-path=.rustfmt.unstable.toml" } },
4. rami3l commented on Sep 9, 2026

   

   rami3l

   on Sep 9, 2026

   MemberAuthor

   More actions

   OTOH to facilitate use in IDEs so that we can never worry about reorganizing imports, I'm discovering the feasibility of adding a recommended rust-analyzer config that looks like so:

   rustfmt = { extraArgs = { "+nightly", "--config-path=.rustfmt.unstable.toml" } },

   Interesting, I cannot use that yet because rust-analyzer is calling rustfmt at the source file's basedir so .rustfmt.unstable-toml will be "not found":

   • Recursive --config-path doesn't recurse rustfmt#4660
5. rami3l

   closed this as completedin #5066on Sep 9, 2026