Rust Live | Introduction to Async Rust
Вставка
- Опубліковано 25 тра 2023
- In this episode, Christy O'Brien hosts Maxwell Flitton to help you get a better understanding and a head start with Asynchronous Rust.
Check out the how you can get involved in our channel here www.amicusjobs.com/community
Amicus Recruitment help businesses connect with the best Software Engineering, Cloud & DevOps and ERP professionals across UK, US & Europe.
We partner with some of the top global brands providing both contract and permanent recruitment solutions when they need us the most.
We are passionate about the tech community and are committed to help drive exposure to these technologies by writing blogs, sharing content, arranging meetups & working on some of the absolute best requirements on the market.
Within every great tech business, are amazingly talented people. Our passion is to connect these people to the organisations who produce some of the best tech products in the world.
🤳🏼 Stay connected!
Website 👉 www.amicusjobs.com/ - Наука та технологія
criminally underrated content, u can't see things like this when u search but have to wait for youtube gods to bless us and show it in home .
Thank you! Glad you enjoyed it.
Now i am also blessed with UA-cam God 😊
I was surprised to see actor model, it's very powerful model. I'd mention location transparency feature in actor based model and possibility to run it on a cluster, so it's very elastic.
Saving this video for tomorrow. Looking forward to it.
Amazing! Hope you enjoyed it!
Tried to watch this but I need an intro to this intro it was way too complex for me
can you show us some filter examples ?
Eu até quero aprender Rust, mas este código me parece mais um receita de bolo, a pessoa segue mas nunca entende de fato o que acontece nos bastidores, é impossível criar softwares inspiradores com isso... COMO ENTENDER TUDO ISSO.... É ASSUTADOR!!!!!
but don't we "not block" on the future?
I know it's probably named that way for a reason.
Just reads a bit confusing.
? Hard to tell what you're trying to say, a timestamp might have helped. But We block on futures when we want to join results, usually.
@@GRAYgauss - my bad. It's the "block_on" statement that is used to kick it off
Oh. I understand now. Yeah, the confusion is block_on is used for sequential code. Futures don't get executed on creation, but instead polling them is what actually starts their execution. Video touched on how this leads to something akin to "cooperative green threading." In async code, you can use .await for non-blocking polling. Basically, you can think of .await as control yield points that if the future has not completed, will result in the async caller (of whatever was awaited) yielding and being rescheduled while your futures are executed. This process will continue until the future being awaited returns results at that point the async caller can continue in it's own sequential process until it hits the next await where it may yield again. All other async functions are doing the same thing, executing sequential code til they hit an await, yielding and allowing other schedule fns to be executed. How your async fns/future are actually scheduled and executed is a whole 'nother story, Tokio's executor for instance provides many mechanisms like work-stealing, the cooperative await yield, task prioritization, etc.@@jeffg4686
@@jeffg4686 Hey I'm the guy who's giving the talk in the video. Once you spawn a task, the task is then getting polled and executed on one of the threads. The block_on function in the main thread is to block the main thread until the task and finished. However, you can perform other processes in the main thread whilst the task is being executed in the other thread until you call the block_on function
круто