tweaking here and there, plans for the future

[rust-101.git] / src / part03.rs

diff --git a/src/part03.rs b/src/part03.rs
index f76c4aaf4a498867f3bb13266d53700e32e5530e..45caaec1557685dcc464dc01984c4a61d234204e 100644 (file)
--- a/src/part03.rs
+++ b/src/part03.rs
@@ -1,5 +1,5 @@
-// Rust-101, Part 03: Input, Testing
-// =================================
+// Rust-101, Part 03: Input
+// ========================
 
 // In part 00, I promised that we would eventually replace `read_vec` by a function
 // that actually asks the user to enter a bunch of numbers. Unfortunately,
@@ -76,7 +76,7 @@ fn read_vec() -> Vec<i32> {
 // as the documentation is quite easy to navigate and you should get used to that.
 
 // For the rest of the code, we just re-use part 02 by importing it with `use`.
-// I already sneaked a bunch of `pub` in the other module to make this possible: Only
+// I already sneaked a bunch of `pub` in part 02 to make this possible: Only
 // items declared public can be imported elsewhere.
 use part02::{SomethingOrNothing,Something,Nothing,vec_min};
 
@@ -88,7 +88,7 @@ pub fn main() {
     min.print();
 }
 
-// **Exercise**: Define a trait `Print` to write a generic version of `SomethingOrNothing::print`.
+// **Exercise 03.1**: Define a trait `Print` to write a generic version of `SomethingOrNothing::print`.
 // Implement that trait for `i32`, and change the code above to use it.
 // I will again provide a skeleton for this solution. It also shows how to attach bounds to generic
 // implementations (just compare it to the `impl` block from the previous exercise).
@@ -103,7 +103,7 @@ trait Print {
 }
 impl<T: Print> SomethingOrNothing<T> {
     fn print2(self) {
-        panic!("Not yet implemented.")
+        unimplemented!()
     }
 }