fmt bug for tuple type access

[He1pa]

I tried this code:

fn main() {
    type Foo = ((i32, i32), i32);
    let a: Foo = ((1, 1), 1);
    let b = a.0.0;
}

And i used fmt(both rust analyzer and cargo fmt)

I expected to see this happen:

fn main() {
    type Foo = ((i32, i32), i32);
    let a: Foo = ((1, 1), 1);
    let b = a.0.0;
}

Instead, this happened:

fn main() {
    type Foo = ((i32, i32), i32);
    let a: Foo = ((1, 1), 1);
    let b = a.0 .0;
}

In a.0 .0，There's an extra space here.

Meta

rustc --version --verbose:

rustc 1.76.0-nightly (3a85a5cfe 2023-11-20)
binary: rustc
commit-hash: 3a85a5cfe7884f94e3cb29a606913d7989ad9b48
commit-date: 2023-11-20
host: aarch64-apple-darwin
release: 1.76.0-nightly
LLVM version: 17.0.5

Backtrace

<backtrace>

[y21]

The extra space used to be necessary in older versions of Rust where tuple.0.0 was a syntax error, and (to my knowledge) rustfmt generally won't change formatting later on, at least with the default version = "One".

If you set version = "Two" in your rustfmt.toml file, it should format this without the extra space as you expect.

See rust-lang/rustfmt#4355 (comment) for more context

[workingjubilee]

Duplicate with rust-lang/rustfmt#4779