rustfmt putting space between first and second tuple element indexing. is this intended?

[bindsdev]

I noticed that rustfmt, in some cases when using tuple indexing back to back such as some_tuple.0.0 (some_tuple.0 being another tuple or tuple struct of course), it would reformat it to some_tuple.0 .0. Is this behavior intended? If so, I would like an explanation on why rustfmt decides to format it this way.

Examples

Prior to running cargo fmt:

match self.peek().1.0 {
    ...
}

match self.advance().1.0 {
    ...
}

if self.peek().1.0 == expected {
   ...
}

After running cargo fmt:

match self.peek().1 .0 {
    ...
}

match self.advance().1 .0 {
    ...
}

if self.peek().1 .0 == expected {
   ...
}

[calebcartwright]

Please see - #4355 (comment)

[bindsdev]

Please see - #4355 (comment)

Thank you.