Trouble with enums2

[Charles-Thacher]

Hi all. My solution to enums2 seems to be correct, even according to another Q&A here (#2079), but Rustlings is giving me a strange output that I do not know how to interpret.

Here is my code, based on the current version:

#[derive(Debug)]
struct Point {
    x: u64,
    y: u64,
}

#[derive(Debug)]
enum Message {
    // TODO: Define the different variants used below.
    Resize {width: i32, height: i32},
    Move(Point),
    Echo(String),
    ChangeColor(u8, u8, u8),
    Quit,
}

impl Message {
    fn call(&self) {
        println!("{self:?}");
    }
}

fn main() {
    let messages = [
        Message::Resize {
            width: 10,
            height: 30,
        },
        Message::Move(Point { x: 10, y: 15 }),
        Message::Echo(String::from("hello world")),
        Message::ChangeColor(200, 255, 255),
        Message::Quit,
    ];

    for message in &messages {
        message.call();
    }
}

I've got the proper implementation of the Point struct, I believe, and my interpreter in Codium says my enums2.rs is error free.

Here is the output from Rustlings:

warning: unused variable: message
--> exercises\08_enums\enums3.rs:46:27
|
46 | fn process(&mut self, message: Message) {
| ^^^^^^^ help: if this is intentional, prefix it with an underscore: _message
|
= note: #[warn(unused_variables)] on by default

running 1 test
test tests::test_match_message_call ... FAILED

failures:

---- tests::test_match_message_call stdout ----
thread 'tests::test_match_message_call' panicked at exercises\08_enums\enums3.rs:80:9:
assertion left == right failed
left: 0
right: 10
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

failures:
tests::test_match_message_call

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

error: test failed, to rerun pass --bin enums3

[mo8it]

It is giving you the output for the next exercise, enum3, which is similar to enum2. See the file name in the error message.

[Charles-Thacher]

Oh, wow, that was silly of me. Probably hit n without realizing it. Thank you!