Would backport of chain_width to 1.4.x be considered?

[ctz]

Hello,

Thank you for your work on rustfmt!

Over in rustls we're using rustfmt 2.0 (built from source), because we're using the chain_width option reintroduced in this version. I've read in #4582 the issues with releasing/stabilising 2.0, and these seem clear to me.

However, would the maintainers accept a PR that backported support for chain_width to the 1.4 release line?

Thanks,
Joe

[calebcartwright]

Absolutely! I was actually already planning to backport the changes that made the granular *_width options (includes chain_width) public and available to users.

Doing so is second on my rustfmt code/development to-do list, though most of my bandwidth these days is preoccupied with the typical admin/support/maintenance/etc. work so not sure exactly when I'd be able to get around to it myself.

PRs are always appreciated as well, but this is definitely something that will get done either way.

[InsertCreativityHere]

Hey there @ctz!
I was wondering if you were going forward with your PR, because otherwise I was going to write one myself!
I'm in the same boat as you, building 2.0 from source to get chain_width and fn_call_width, and it would be real nice to have it in 1.4.x instead! 😄

[karyon]

@calebcartwright after #4782 has been merged, is there anything left to do here?

[ctz]

This was done, merged and was released.

[karyon]

(I think the last release 1.4.37 was done before the backport was merged, so it's not released yet)

[calebcartwright]

(I think the last release 1.4.37 was done before the backport was merged, so it's not released yet)

I forget the exact path it took to get there, but this was one that got deployed a while ago (has been around since Rust v1.53). Either way, backport definitely completed 😁