Concurrency in Rust - Creating Threads

[@letsgetrusty]

📝 Get your *FREE Rust cheat sheet* : www.letsgetrusty.com/cheatsheet

[@sonicsplasher]

Just 15 videos to go. You got this

[@everyhandletaken]

I was expecting that to be more complicated.. nice 👍🏻

[@magnoelmagnifico957]

me too haha

[@jonathanmoore5619]

That's the next part...

[@everyhandletaken]

@@jonathanmoore5619 calm before the storm ☺️

[@veirt]

Ikr, the chapter before (smart pointers) was hell for me who came from high level languages

[@everyhandletaken]

@@veirt I can relate, most things are hell for me 😂

[@yousefh4939]

i will rewatch all the videos after it get complete it make me happy to see you made new video every time i log in youtube

[@exoticcoder5365]

Very useful & clear on why we need to move ownwership into the closure 👍🏻Thank you

[@aloysberger9482]

Good work mate, thank you for these videos they're very good. Keep up the good work.

[@kishanbsh]

Eagerly awaiting your video on async await and futures

[@herrxerex8484]

Keep it up , man !!! awesome as always

[@ClaudioParraGonzalez]

Sweet stuff! Thanks, man!

[@----__---]

eagerly waiting for listening to the async by you

[@aqua3418]

Don't you mean you're _awaiting_ for him to explain it? **nudge nudge**

[@mybdretaemch3409]

this is very interesting!! nice explanation!

[@MrGreen-kq4ds]

great video - thanks! do u plan to cover async rust at some point?

[@letsgetrusty]

Yes!

[@bgdjovan]

Really useful!

[@func0der]

Thank you very much for this clear video. I learned so much.

[@spongechameleon6940]

Is there an idiomatic way to pass the same data in heap to multiple threads for reads? Like by wrapping the data in Rc?

[@cat-.-]

std::sync::Arc

[@emvdl]

Thank you! 👍

[@alanaxotla9112]

This is amazing

[@jabuci]

Can you make a video about scoped threads? New in 1.63.

[@TON-vz3pe]

How is race condition and dead lock. prevented in this example?

[@mdrealiyev]

Hello. Evertig is good and understandable. But I have a question. How can I call thread::spawn inside implemented class and pass self safety?

[@KokahZ777]

I pattern I found is to wrap your struct (call it A) data in some Inner struct that is Arc in A That way you can pass a self clone to your functions which just duplicates the pointer but not the actual data

[@saadabbasi2063]

Please make a video on using Tokio

[@letsgetrusty]

I will eventually!

[@emilfilipov169]

I find this confusing and I can't find anyone who has explained it yet. So, the thread takes ownership of your variable, say v, for example. You "can't" use it outside of the thread, but yet you can. fn main() { let limit: i32 = 5; let handle = thread::spawn(move || { for n in 1..=limit { println!("Spawned, {}", n * n); thread::sleep(Duration::from_millis(1)) } }); for n in 1..=limit { println!("Main, {}", n * n); thread::sleep(Duration::from_millis(1)) } handle.join().unwrap(); } Why does this code run? If one thread has ownership of the variable, doesn't that mean nothing else can own it?

[@kylezwarich]

The move keyword for closure tells Rust compiler to keep "limit" in scope for the duration of the spawned thread, and handle.join().unwrap() says to run all threads through to completion. So every loop iteration the spawned thread asks "is limit still a thing", Rust says "it is a thing because you still need it"; even though the main thread might have finished processing its batch of loops already, the other still needs access to 'limit'. If me and you order spaghetti and meatballs, but I hate noodles and you hate meatballs, we can split the dish and we both have a satisfying meal, but we have to share the fork. Just because I'm finished all the meatballs doesn't necessarily mean our dinner is done--using the move keyword and the thread::join() says "we both need the fork so don't get rid of it until we're both done the plate"

[@janedoe6182]

"As soon as you type new Thread(), it’s over; your project already has legacy code" (c) Stephen Cleary In general creating new OS threads in modern programs - bad idea. Except specialized pools serving async I/O

[@hobbes5043]

I thought this video was alright. I wish you did more than just rehash the textbook though. Some different examples would have helped.

[@alexisgavidia3141]

hi, i have a question if !l.iter().any(|x| x.file_name == j.file_name) { //copy file to tmp folder. let y = j.clone(); let ha = thread::spawn(move || async move { cp_to_tmp_and_pod( cmd_start_raw_capture_ecs, y, i, pods, n, &path_on_the_host, ) .await; }); n += 1; l.push(j); ha.join().unwrap().await; } } ha.join().unwrap().await; i cant run it the function wiout the await. and i want to run but the main thred need to wait until this fisnih.