Tracking issue for unstable option: `imports_granularity`. [Option documentation.](https://rust-lang.github.io/rustfmt/#imports_granularity) See [Processes.md, "Stabilising an Option"](https://github.com/rust-lang/rustfmt/blob/master/Processes.md#stabilising-an-option): - [x] Is the default value correct? - [x] The design and implementation of the option are sound and clean. - [x] The option is well tested, both in unit tests and, optimally, in real usage. - [ ] There is no open bug about the option that prevents its use. - [x] #5269 - [ ] #6028 - [ ] #6027 - [ ] https://github.com/rust-lang/rustfmt/issues/6666 - [ ] https://github.com/rust-lang/rustfmt/issues/6717 - [x] https://github.com/rust-lang/rustfmt/issues/6191 - [x] #5030 - [x] #4681 - [x] #5253 - [ ] https://github.com/rust-lang/rustfmt/issues/6164 - [x] #5311 - [ ] #5296 - [x] #4406 - [x] #4536 - [x] #3984 - [x] #3999 - [ ] #6195 - [ ] #6241 - [x] #6243
Tracking issue for unstable option:
imports_granularity.Option documentation.
See Processes.md, "Stabilising an Option":
imports_granularityis not respected for#[cfg]'d items #6666imports_granularity=Oneremoves macro imports that share names with modules #6717imports_granularity = "Module"merges top-level modules into a singleusestatement #6191imports_granularity=Itemremoves#[cfg()]attribute from imports #5030imports_granularity = "Module"causes compile error when path containsself#4681imports_granularity = "Module"doesn't work if module path is too long #6164uses #3984usestatements arounds comments, changing their meaning #6241