BUG: Fails to keep a space before range .. when its LHS is a binary operation whose RHS is a float literal ending with .

[TonalidadeHidrica]

I wonder how I can make the title short 🤔

In the following code, the space between 1. and .. must be kept, as together they form an illegal token ....

fn main() {
    let a = 0. + 1. ..2.;
}

Expected: no changes, found:

fn main() {
    let a = 0. + 1...2.;
}

Related: #3854 , but it only handles the case when LHS of .. is not a binary expression. Indeed, this code is not modified by rustfmt as expected:

fn main() {
    let a = 1. ..2.;
}

[ytmimi]

Duplicate of #6059, and should already be fixed by #6085. Just hasn't been released yet.

[TonalidadeHidrica]

It still presists on nightly build. Isn't the nightly build from the master branch d5f1200, which is later than the merge commit 73c8149?

$ pbpaste
fn main() {
    let a = 0. + 1. ..2.;
}
$ pbpaste | rustfmt +nightly
fn main() {
    let a = 0. + 1...2.;
}
$ rustfmt +nightly --version
rustfmt 1.7.0-nightly (8679004 2024-05-23)

[ytmimi]

Nope!

rustfmt and some other dev tools are git subtrees of the rust-lang/rust repo. rustfmt is developed here in rust-lang/rustfmt, but it's released from the in-tree source in rust-lang/rust.

Part of rustfmt's release process is syncing changes here with rust-lang/rust. Until we do our sync the changes won't be released.

[TonalidadeHidrica]

Ah, that makes sense! Thank you for kindly telling me about it, and I am sorry for having disturbed you.

[ytmimi]

No worries. It can definitely be confusing!