This is shows the difference in Move behavior between a boxed struct whose members can be copied and a box struct whose members can't be copied.

destructure-copyable-vs-uncopyable.rs

// THANKS TO https://rustbyexample.com/std/box.html
// for the code that was modified into this example

struct Point {
    x: f64,
    y: f64,
}

struct Rectangle {
    p1: Point,
    p2: Point,
}

fn origin() -> Point {
    Point { x: 0.0, y: 0.0 }
}

fn main() {

    //make a boxed point and boxed rectangle
    let boxed_rectangle: Box<Rectangle> = Box::new(Rectangle {
        p1: origin(),
        p2: origin()
    });

    let boxed_point: Box<Point> = Box::new(origin());

    // we can't destructure the boxed rectangle
    //   let p1 = boxed_rectangle.p1;
    //   let p2 = boxed_rectangle.p2; <------ error: use of moved value 'boxed_rectangle'
 
    // instead, we have to dereference the box, then destructure:
    
    
    // required because point can't be copied    
    let unboxed_rectangle = *boxed_rectangle;
    let p1 = unboxed_rectangle.p1;
    let p2 = unboxed_rectangle.p2;
    
    // ok because `x` and `y` are float-64s, which can be copied
    let x = boxed_point.x;
    let y = boxed_point.y;

}