X-Git-Url: https://git.ralfj.de/rust-101.git/blobdiff_plain/c25f3400060ea1a02f8fa9de69c39fd7b020e8a5..9f9b301fd5e86ae4b8cf743f80a129e4addb3635:/src/part00.rs?ds=sidebyside diff --git a/src/part00.rs b/src/part00.rs index 6469907..d126a17 100644 --- a/src/part00.rs +++ b/src/part00.rs @@ -37,7 +37,7 @@ fn vec_min(vec: Vec) -> NumberOrNothing { // Now we want to *iterate* over the list. Rust has some nice syntax for iterators: for el in vec { - // So `el` is al element of the list. We need to update `min` accordingly, but how do we get the current + // So `el` is an element of the list. We need to update `min` accordingly, but how do we get the current // number in there? This is what pattern matching can do: match min { // In this case (*arm*) of the `match`, `min` is currently nothing, so let's just make it the number `el`. @@ -51,6 +51,8 @@ fn vec_min(vec: Vec) -> NumberOrNothing { min = NumberOrNothing::Number(new_min); /*@*/ } } + //@ Notice that Rust makes sure you did not forget to handle any case in your `match`. We say + //@ that the pattern matching has to be *exhaustive*. } // Finally, we return the result of the computation. return min; @@ -70,13 +72,13 @@ fn min_i32(a: i32, b: i32) -> i32 { // Indeed, we can: The following line tells Rust to take // the constructors of `NumberOrNothing` into the local namespace. -// Try moving that above the function, and removing all the occurrences `NumberOrNothing::`. +// Try moving that above the function, and removing all the occurrences of `NumberOrNothing::`. use self::NumberOrNothing::{Number,Nothing}; // To call this function, we now just need a list. Of course, ultimately we want to ask the user for // a list of numbers, but for now, let's just hard-code something. -//@ `vec!` is a *macro* (as you can tell from the `!`) that constructs a constant `Vec<_>` with the given +//@ `vec!` is a *macro* (as indicated by `!`) that constructs a constant `Vec<_>` with the given //@ elements. fn read_vec() -> Vec { vec![18,5,7,1,9,27] /*@*/ @@ -108,7 +110,7 @@ pub fn main() { // Finally, try `cargo run` on the console to run it. //@ Yay, it said "1"! That's actually the right answer. Okay, we could have -//@ computed that ourselves, but that's besides the point. More importantly: +//@ computed that ourselves, but that's beside the point. More importantly: //@ You completed the first part of the course. -//@ [index](main.html) | previous | [next](part01.html) +//@ [index](main.html) | previous | [raw source](workspace/src/part00.rs) | [next](part01.html)