Suggest reordering fields for a borrow of a moved value

Code

struct Foo {
    a: String,
    b: usize,
}

impl Foo {
    fn new(a: String) -> Self {
        Self {
            a,
            b: a.len(),
        }
    }
}

Current output

error[E0382]: borrow of moved value: `a`
  --> src/lib.rs:10:16
   |
 7 |     fn new(a: String) -> Self {
   |            - move occurs because `a` has type `String`, which does not implement the `Copy` trait
 8 |         Self {
 9 |             a,
   |             - value moved here
10 |             b: a.len(),
   |                ^ value borrowed here after move
   |
help: consider cloning the value if the performance cost is acceptable
   |
 9 |             a: a.clone(),
   |              +++++++++++

Desired output

error[E0382]: borrow of moved value: `a`
  --> src/lib.rs:10:16
   |
 7 |     fn new(a: String) -> Self {
   |            - move occurs because `a` has type `String`, which does not implement the `Copy` trait
 8 |         Self {
 9 |             a,
   |             - value moved here
10 |             b: a.len(),
   |                ^ value borrowed here after move
   |
help: consider initializing `b` before `a`
   |
 9 |             b: a.len(),
   |             ++++++++++++
10 |             a,
   |             ++
   |
help: otherwise consider cloning the value if the performance cost is acceptable
   |
 9 |             a: a.clone(),
   |              +++++++++++

Rationale and extra context

No response

Other cases

Rust Version

1.94.0-nightly 2025-12-22

Anything else?

No response

Start by reproducing the E0382 diagnostic with the Rust example in the issue and inspect the compiler's handling of this borrow-after-move case. Done means the diagnostic suggests initializing b before a while retaining the existing cloning suggestion, with coverage for the shown example and relevant other cases.