The rust_analyser extension will display the error 'rust-analyzer failed to discover workspace' in vscode because it doesn't like many separate Rust projects in a single opened folder.

Added a workspace, if the cloner of this repo opens the workspace instead of the folder all projects will be properly parsed and analysed by Rust.

I am leaning rust and taking your course (on skillshare if you are currious)) and everything have been super clear so far, the only thing I haven't liked is that you say

    // Time for some fun with threads and channels!  Though there is a primitive type of channel
    // in the std::sync::mpsc module, I recommend always using channels from the crossbeam crate,
    // which is what we will use here.

Without giving a reason why you prefer the crate over the std library. Do you have an article (or know of one) which goes into why crossbeam is better than the std library, or maybe the reason is so simple you can summerize it in a sentence or two?

The video chapters/lessons never mentions channels either, so as I don't know what channel:: is I have a hard time even understanding it and its user cases.

Hi, just doing the excersise G-COLLECTIONS_ENUMS and I'm stuck on the last point 3, looping through shots. I'm not really sure how to fix this.

here is my code:

// Silence some warnings that could distract from the exercise
#![allow(unused_variables, unused_mut, dead_code)]

// Someone is shooting arrows at a target.  We need to classify the shots.
//
// 1a. Create an enum called `Shot` with variants:
// - `Bullseye`
// - `Hit`, containing the distance from the center (an f64)
// - `Miss`
//
// You will need to complete 1b as well before you will be able to run this program successfully.
enum Shot {
    Bullseye,
    Hit(f64),
    Miss,
}

impl Shot {
    // Here is a method for the `Shot` enum you just defined.
    fn points(self) -> i32 {
        match self {
            Shot::Bullseye => 5,
            Shot::Hit(x) => {
                if x < 3.0 {
                    2
                } else {
                    1
                }
            },
            Shot::Miss => 0
        }
        // 1b. Implement this method to convert a Shot into points
        // - return 5 points if `self` is a `Shot::Bullseye`
        // - return 2 points if `self` is a `Shot::Hit(x)` where x < 3.0
        // - return 1 point if `self` is a `Shot::Hit(x)` where x >= 3.0
        // - return 0 points if `self` is a Miss
    }
}

fn main() {
    // Simulate shooting a bunch of arrows and gathering their coordinates on the target.
    let arrow_coords: Vec<Coord> = get_arrow_coords(5);
    let mut shots: Vec<Shot> = Vec::new();

    // 2. For each coord in arrow_coords:
    //
    //   A. Call `coord.print_description()`
    //   B. Create the correct variant of `Shot` depending on the value of
    //   `coord.distance_from_center()`
    //      - Less than 1.0 -- `Shot::Bullseye`
    //      - Between 1.0 and 5.0 -- `Shot::Hit(value)`
    //      - Greater than 5.0 -- `Shot::Miss`

    for coord in arrow_coords.iter() {
        coord.print_description();

        if coord.distance_from_center() > 1.0 {
            shots.push(Shot::Bullseye);
        } else if coord.distance_from_center() >= 1.0 && coord.distance_from_center() <= 5.0 {
            shots.push(Shot::Hit(coord.distance_from_center()))
        } else {
            shots.push(Shot::Miss);
        }
    }

    let mut total = 0;
    // 3. Finally, loop through each shot in shots and add its points to total
    
    for shot  in shots.iter() {
        total += shot.points();
    }

    println!("Final point total is: {}", total);
}

The error is pointing at line toal += shot.points() saying

move occurs because *shot has type Shot, which does not implement the Copy trait

I know what it means, but I don't know how to get it working. Thank you!

I just wrote fn add(a: &i32, b: &i32) -> i32 {a+b} which works correctly, is that intended? There seems to be no manual dereferencing needed, has that changed since your created the exercises? Or is the correct answer *a+*b with explicit dereferencing?

  // Challenge: Write a function "add" that takes *references* to two integer arguments,
    // dereferences them and adds them together, and returns the result.
    //
    println!("1 + 2 = {}, even via references", add(&1, &2));   

I come across this small TYPO in final exercise:

https://github.com/CleanCut/ultimate_rust_crash_course/blob/ccb6cd213bb8ce4a1ff2026e5113aa39b17d5fb7/exercise/z_final_project/src/main.rs#L158-L159

Based on official documentation .grayscale() returns a new image (please see rust doc)

pub fn grayscale(&self) -> DynamicImage { ... }

PS: Great course full of very useful tips and great exercises. Looking forward for your upcoming rust course.

Hey there, I'm working through the first exercise and reviewing the answers. I see there's a reference to a loaded variable, but I don't see this mentioned in the readme instructions. Perhaps this was meant to be ready? Small nitpick but thought you might like to know! If not, no worries. Have a good one 👋

Hello!

I have renamed the packages to their snake case name in order to comply with RFC 940.

Since that standard packages and crates containing hyphens in their name are not supported by the rust compiler but they are supported by Cargo.

If a student implements a function in the src/lib.rs file of any of these packages, then importing that function will produce a compile error that may cause confusion in the student.

For example, in exercise E some students may choose to implement the function inspect in src/lib.rs. When trying to import this function in src/main.rs using the following use statement:

use e-ownership-references::inspect;

Will produce a compiler error:

error: expected one of `::`, `;`, or `as`, found `-`
 --> src/main.rs:4:6
  |
4 | use e-ownership-references::inspect;
  |      ^ expected one of `::`, `;`, or `as`

error: aborting due to previous error

error: could not compile `e-ownership-references`

Also quoting the package name will not resolve the issue as specified in RFC 940.

The only way to solve this error is by replacing all the hyphens with _ which may cause confusion among students.

I have also corrected a couple of comments in exercise H.

Great course BTW 😄 !

Not sure if you want this change but I get a compiler warning when running cargo run on this project before I start solving it. I noticed that we are disabling warnings for unused mut so figured we should be ignoring variables as well?

koddsson@Kristjans-MBP e_ownership_references % cargo run
   Compiling e_ownership_references v0.1.0 (/Users/koddsson/src/koddsson/ultimate_rust_crash_course/exercise/e_ownership_references)
warning: unused variable: `arg`
 --> src/main.rs:7:13
  |
7 |     let mut arg: String = std::env::args().nth(1).unwrap_or_else(|| {
  |             ^^^ help: if this is intentional, prefix it with an underscore: `_arg`
  |
  = note: `#[warn(unused_variables)]` on by default

warning: `e_ownership_references` (bin "e_ownership_references") generated 1 warning
    Finished dev [unoptimized + debuginfo] target(s) in 0.71s
     Running `target/debug/e_ownership_references`
Please supply an argument to this program.

I'm updating a bunch of things to correspond to the big video content refresh I'm doing for the course.

I'll merge this at the same time I update the course online.