[unstable option] imports_layout

[scampi]

Tracking issue for unstable option: imports_layout

[jimmycuadra]

What's necessary to stabilize this?

[scampi]

There are some steps described in https://github.com/rust-lang/rustfmt/blob/master/Processes.md#stabilising-an-option.
#3581 is an attempt at this.

[mzabaluev]

Why does Horizontal have to exceed max_width?
How does this behavior interact with merge_imports = true?

I think it should be possible to try to fit all import statements into max_width, replicating the path prefix for any spill-over items into the next line(s).

[mzabaluev]

One good reason to prefer the Horizontal layout (and stabilize this setting after the behavioral aspects are ironed out) is to keep the imports searchable with grep-like tools that don't easily match across multiple lines.

[andreastt]

A counter-argument for Vertical sorting is that it makes rebases significantly easier.

I recently had to do a rebase of a fairly complicated refactoring that moved lots of types around, and git rebase tools for in-line changes is not great.

I would like to use this feature in mozilla-central once it’s stablised.

[vn971]

I would love independent imports:

use foo::{
    aaaaaaaaaaaaaaaaaa, bbbbbbbbbbbbbbbbbb, cccccccccccccccccc, dddddddddddddddddd,
    eeeeeeeeeeeeeeeeee, ffffffffffffffffff,
};

=>

use foo::aaaaaaaaaaaaaaaaaa;
use foo::bbbbbbbbbbbbbbbbbb;
use foo::cccccccccccccccccc;
use foo::dddddddddddddddddd;
use foo::eeeeeeeeeeeeeeeeee;
use foo::ffffffffffffffffff;

As a possible alternative, I find this style super-friendly to git, immediately readable to my tastes, easy to play around with commenting-uncommenting.

Is it possible to have it as an independent alternative option?

UPDATE: for unstable rustfmt, this has been implemented as Item granularity 🎉

[dtolnay]

I think "independent imports" (#3361 (comment)) is outside of what this option is for, and is a discussion for #3362 instead. It's already been brought up there in #3362 (comment).

AIUI the two options are orthogonal and the distinction is as follows: you can think of merge_imports as determining the tokens of our imports i.e. how/whether they should be grouped i.e. which parts of which specific paths should go inside of the same curly braces; while imports_layout determines the whitespace of each import after the point that the tokens have already been decided.

[Lokathor]

Shouldn't "mixed' be called "compressed" to match other similar options?

[calebcartwright]

To explain for new people reading this issue. imports_layout is not going to be stabilized and is instead replaced with imports_granularity #3362 (comment)

This is incorrect. merge_imports was superseded by imports_granularity, there was no impact and no change to imports_layout which was a different option that controlled different formatting aspects.