X-Git-Url: https://git.ralfj.de/rust-101.git/blobdiff_plain/fff8ebeb3f0b84c71275cbb5adee0aad6114f79b..57fd78e47f3f9d935f62a5dc05e8676ae035ad3d:/workspace/src/part00.rs?ds=inline diff --git a/workspace/src/part00.rs b/workspace/src/part00.rs index 65769ef..9144eae 100644 --- a/workspace/src/part00.rs +++ b/workspace/src/part00.rs @@ -1,5 +1,3 @@ -// ***Remember to enable/add this part in `main.rs`!*** - // Rust-101, Part 00: Algebraic datatypes // ====================================== @@ -19,7 +17,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`. @@ -50,7 +48,7 @@ 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 @@ -60,8 +58,7 @@ fn read_vec() -> Vec { unimplemented!() } -// Finally, let's call our functions and run the code! -// But, wait, we would like to actually see something, so we need to print the result. +// Of course, we would also like to actually see the result of the computation, so we need to print the result. fn print_number_or_nothing(n: NumberOrNothing) { unimplemented!() @@ -74,7 +71,6 @@ pub fn main() { print_number_or_nothing(min); } -// You can now use `cargo build` to compile your code. If all goes well, try `cargo run` on the -// console to run it. +// Finally, try `cargo run` on the console to run it.