// Rust-101, Part 01: Expressions, Inherent methods
// ================================================
// Rust-101, Part 01: Expressions, Inherent methods
// ================================================
// Even though our code from the first part works, we can still learn a
// lot by making it prettier. To understand how, it is important to
// understand that Rust is an "expression-based" language. This means that most of the
// terms you write down are not just *statements* (executing code), but *expressions*
// (returning a value). This applies even to the body of entire functions!
// Even though our code from the first part works, we can still learn a
// lot by making it prettier. To understand how, it is important to
// understand that Rust is an "expression-based" language. This means that most of the
// terms you write down are not just *statements* (executing code), but *expressions*
// (returning a value). This applies even to the body of entire functions!
// For example, consider `sqr`:
fn sqr(i: i32) -> i32 { i * i }
// Between the curly braces, we are giving the *expression* that computes the return value.
// For example, consider `sqr`:
fn sqr(i: i32) -> i32 { i * i }
// Between the curly braces, we are giving the *expression* that computes the return value.
+ // Remember that helper function `min_i32`? Rust allows us to define such helper functions *inside* other
+ // functions. This is just a matter of namespacing, the inner function has no access to the data of the outer
+ // one. Still, being able to nicely group functions can be very useful.
+ fn min_i32(a: i32, b: i32) -> i32 {
+ if a < b { a } else { b }
+ }
+
// Now that's already much shorter! Make sure you can go over the code above and actually understand
// every step of what's going on.
// Now that's already much shorter! Make sure you can go over the code above and actually understand
// every step of what's going on.
// So much for `vec_min`. Let us now reconsider `print_number_or_nothing`. That function
// really belongs pretty close to the type `NumberOrNothing`. In C++ or Java, you would
// probably make it a method of the type. In Rust, we can achieve something very similar
// So much for `vec_min`. Let us now reconsider `print_number_or_nothing`. That function
// really belongs pretty close to the type `NumberOrNothing`. In C++ or Java, you would
// probably make it a method of the type. In Rust, we can achieve something very similar
// You will have to replace `part00` by `part01` in the `main` function in
// `main.rs` to run this code.
// You will have to replace `part00` by `part01` in the `main` function in
// `main.rs` to run this code.
-// **Exercise 01.1**: Write a funtion `vec_avg` that computes the average value of a `Vec<i32>`.
-//
-// *Hint*: `vec.len()` returns the length of a vector `vec`.
+// **Exercise 01.1**: Write a funtion `vec_sum` that computes the sum of all values of a `Vec<i32>`.
+
+// **Exercise 01.2**: Write a function `vec_print` that takes a vector and prints all its elements.