Merge pull request #31 from BBlackwo/misc-updates

Update 08 quiz solution and some typo fixes

Author: sb1752

Diff for: 05_vectors_and_result_enum.md

@@ -102,7 +102,7 @@ Crashing your program is probably not the best way to handle an error, unless yo
 For now we'll use the `unwrap` method.
 We'll explore different ways of handling a `Result` and doing proper error handling later on in this course.
 
-For now, let's our function so that we are actually working with the underlying vector of bytes and not the wrapped `Result` type:
+For now, let's update our function so that we are actually working with the underlying vector of bytes and not the wrapped `Result` type:
 
 ```rust
 fn read_version(transaction_hex: &str) -> u32 {

Diff for: 08_traits_and_reading_bytes.md

@@ -91,7 +91,7 @@ pub trait Read {
 
 You'll notice there's no function body, just the signature.
 It means the `read` method itself is not actually implemented with any logic in the trait declaration.
-We expect the types that "implement" this trait to aactually provide the function logic for any *required* method, or trait methods, that have no implementation.
+We expect the types that "implement" this trait to actually provide the function logic for any *required* method, or trait methods, that have no implementation.
 
 A trait can also provide other methods that a type can get access to once it has implemented the trait.
 These are known as *provided* methods and are considered *default* implementations since they can also be overwritten.

Diff for: README.md

@@ -43,3 +43,4 @@ By the end of this project, you will have understood the fundamental concepts of
 * [20.0 Command Line Arguments](20_command_line_arguments.md)
 * [21.0 Refactoring and the Rust-Bitcoin Library](21_refactoring_and_rust_bitcoin.md)
 * [22.0 Decoding Segwit](22_decoding_segwit.md)
+* [Quiz Solutions](quiz_solutions/)

Diff for: quiz_solutions/08_solution.md

@@ -44,24 +44,26 @@ For now, if we wanted to print a `vec` we would have to use `{:?}` inside the pr
 
 Let's attempt to implement the `Display` trait for a `vec` by implementing the required method `fmt`:
 ```rust
-use std::fmt;
+use std::fmt::{self, Display, Formatter};
 
-impl Display for Vec<u8> {
+struct CustomVec<T>(Vec<T>);
+
+impl Display for CustomVec<u8> {
     fn fmt(&self, f: &mut Formatter<'_>) -> fmt::Result {
         write!(f, "Values:\n")?;
-        for v in &self {
+        for v in &self.0 {
             write!(f, "\t{}", v)?;
         }
         Ok(())
     }
 }
 
 fn main() {
-    let vec: Vec::<u8> = vec![0, 0, 0, 0, 0];
+    let vec: CustomVec<u8> = CustomVec(vec![0, 0, 0, 0, 0]);
     println!("Vec: {}", vec);
 }
 ```
 
-The basic idea is that we leverage the `write!` macro which takes the `Formatter` instance and writes some information to it. If any step fails, an error will be returned (we'll talk more about error handling and the `?` operator in chapter 19). If we iterate through the vector and are able to write all values successfully we can simply return the `Ok(())` result, which matches the the expected result type `fmt::Result`. 
+The basic idea is that we leverage the `write!` macro which takes the `Formatter` instance and writes some information to it. If any step fails, an error will be returned (we'll talk more about error handling and the `?` operator in chapter 19). If we iterate through the vector and are able to write all values successfully we can simply return the `Ok(())` result, which matches the the expected result type `fmt::Result`. We need to create a `CustomVec<T>` using the [Newtype Pattern](https://doc.rust-lang.org/book/ch19-03-advanced-traits.html#using-the-newtype-pattern-to-implement-external-traits-on-external-types) to implement external traits on external types.
 
 This might still be a bit confusing at this stage, so consider coming back to revisit this solution after you've gone through the course.