+// With this fresh knowledge, let us now refactor `vec_min`.
+fn vec_min(v: Vec<i32>) -> NumberOrNothing {
+ let mut min = Nothing;
+ for e in v {
+ // Notice that all we do here is compute a new value for `min`, and that it will always end
+ // up being a `Number` rather than `Nothing`. In Rust, the structure of the code
+ // can express this uniformity.
+ min = Number(match min {
+ Nothing => e,
+ Number(n) => std::cmp::min(n, e)
+ });
+ }
+ // The `return` keyword exists in Rust, but it is rarely used. Instead, we typically
+ // make use of the fact that the entire function body is an expression, so we can just
+ // write down the desired return value.
+ min
+}
+
+// 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
+// by providing an *inherent implementation*.
+impl NumberOrNothing {
+ fn print(self) {
+ match self {
+ Nothing => println!("The number is: <nothing>"),
+ Number(n) => println!("The number is: {}", n),
+ };
+ }
+}
+// So, what just happened? Rust separates code from data, so the definition of the
+// methods on an `enum` (and also on `struct`, which we will learn about later)
+// is independent of the definition of the type. `self` is like `this` in other
+// languages, and its type is always implicit. So `print` is now a method that
+// takes as first argument a `NumberOrNothing`, just like `print_number_or_nothing`.
+//
+// Try making `number_or_default` from above an inherent method as well!