Chains style and the await keyword

[Samuel-B-D]

I believe the style guideline about multi-line chains should be revised to not treat keyword the same way as it treat fields or methods.
I subjectively think that it is much more readable to keep the .await on the same line as it's associated future, and I think that the 2nd following snippet is much more readable:

#[tokio::main]
async fn main() -> reqwest::Result<()> {
    reqwest::Client::new()
        .get("http://example.org")
        .send()
        .await?
        .text()
        .await?;
    Ok(())
}

#[tokio::main]
async fn main() -> reqwest::Result<()> {
    reqwest::Client::new()
        .get("http://example.org")
        .send().await?
        .text().await?;
    Ok(())
}

This was initially requested as a configuration option to rust fmt here: rust-lang/rustfmt#4425
but I suspect that the guideline about multiline chain was made before the await keyword was adopted and that the official style guide should probably account for this.

[calebcartwright]

Thanks for sharing your perspective, but I'm going to close. We're working on some things within rustfmt that'll give folks a bit more flexibility, including the ability to keep your awaits on the same line if you choose, but we aren't going to go about giving that flexibility by making a breaking change to the style specification as suggested here.