options3 ref vs &

[eyyyyyyy3]

Why is this way of solving the challenge:

fn main() {
    let y: Option<Point> = Some(Point { x: 100, y: 200 });

    match y {
        Some(ref p) => println!("Co-ordinates are {},{} ", p.x, p.y),
        _ => panic!("no match!"),
    }
    y; // Fix without deleting this line.
}

more preferred than this one:

fn main() {
    let y: Option<Point> = Some(Point { x: 100, y: 200 });

    match &y {
        Some(p) => println!("Co-ordinates are {},{} ", p.x, p.y),
        _ => panic!("no match!"),
    }
    y; // Fix without deleting this line.
}

[sinux-l5d]

I'm also interesed for feedback. I'm learning Rust and my first though was to match &y, before reading about the ref keyword.

[mo8it]

What do you mean with "more preferred"? Is it because the compiler suggests it?

Personally, I prefer the second solution with & over ref. ref is rarely used in the Rust code that I read until now.

[eyyyyyyy3]

Yes. I mean I kinda understand that with ref you can do more advanced pattern matching without deconstructing the tuple on the right hand side. E.g. (ref a, b)