Matching a partially moved value results in weird runtime behavior.

[dpc]

Sorry for not providing smaller case but I hope this is better than nothing:

https://github.com/dpc/rustyhex/blob/broken/src/ui/piston.rs#L744

self.input_controller.push_input(i);
// vs self.input_controller.push_input(i.clone());

Both versions works (compile and start), but runtime behavior changes. The code that follows the above part:

match i {
    Press(Keyboard(_)) => {
           self.game_update(game)
     },

will match Press(Keyboard(_)) no matter what i really is, if the value is partially moved (so mouse events are updating my game). If I use the version with i.clone(), the code works as intended and game is updated only on keyboard presses.

[dpc]

$ rustc --version
rustc 0.12.0-pre (b88d1030e 2014-09-17 18:26:14 +0000)

[ghost]

Minimal:

struct X(int);

impl Drop for X {
    fn drop(&mut self) { }
}

fn main() {
    let foo = X(1i);
    drop(foo);
    match foo {
        X(1i) => (),
        _ => unreachable!()
    }
}

This shouldn't compile at all.

[alexcrichton]

Nominating.

[ghost]

Looks like a regression. 0.10 rejects this code.