Why writing Task in DispatchQueue ? Also 5:31 why we want to halt the main. thread via using `sync` instead of `async` , is it just to return value?

You have great didactic abilities … bravo from 🇨🇭

Very well explained. Keep up the good work.

Awesome awesome explanation brother 🤩🤩. Thank you so much for your all videos 😍

Hey, thanks so much! Why are the queues at the end still needed? Or if they aren't needed, why are you still using them?

Awesome video. Thanks for sharing your knowledge. Helps a lot

Actor concept is Nice , it's really interesting, compare to existing techniques.

Thank you for nice content.

well done very nice explanation 👍

Thank you for awesome video !!!

Learnt something new today. Thank you. What I am more curious about is how the actor is working internally?

Thanks for the nice content

Superb keep posting💪

superbb

Very nice explanation.

Thanks Palav

Nice explanation 👍

Great tutorial. I observed that even when I did not create add keyword "MainActor" and just called the updateLabel method from my Task block, I did NOT get a crash and the setting up the break point inside updateLabel showed that it was on main thread. How is that possible?

Hey pallev, Thanks for the video. Have one question why you used sync on both operations with barrier.I think same could be achieved without using barrier on sync operation (as they already in sync)or async operation with barrier?

Hey pallev, Thanks for this great video. now I have a clear concept of Actor. I would really appreciate if you can come up with one video of Closures. thanks

Very nice sir. thanks

Great Job 👏

Man this guy is good

Interesting trade off. The barrier was neat in the old Flight class. Now the burden to make it properly called, the caller are forced to call with async await.

Hi Pallav, Great fan of yours. In a couple of interviews, I faced this question. "How do you convert struct to a class? or atleast give some functionalities of class to struct." I searched a lot through web but couldn't find any answer. Could you please help me with this.

I learnt the latest topic. Thanks for sharing.

And chance this is usable also for communication between realtime audio thread and main thread ? I mean if you are trying to communicated between realtime audio thread and main thread there are some forbidden things like using of MUTEX - so any chance all this Actors aren’t using MUTEX ?

Impressive ....once again.👏👏👏

Thank you for sharing the valuable information

thanks for the video keep up the good work :)

🎉🎉🎉🎉❤

Thanks for this lesson)))

👍

When should we use weak and unowned in swift?

Hi Pallav, Thanks for the video. I tried with same approach but surprisingly it worked if I used the 2 queue like in your video but whenever I tried with 3 queue it is not working. I am sharing the code snippet for the same. Share your thought on it. actor Flight { var availableSeats = ["1A", "2B", "3C"] func bookSeat() -> String { let bookedSeat = availableSeats.first ?? "" availableSeats.removeFirst() return bookedSeat } func getAvailableSeats() -> [String] { availableSeats } } class ViewController: UIViewController { override func viewDidLoad() { super.viewDidLoad() let flight = Flight() let queue1 = DispatchQueue(label: "queue1") let queue2 = DispatchQueue(label: "queue2") let queue3 = DispatchQueue(label: "queue3") queue1.async { Task { let availableSeats = await flight.getAvailableSeats() print("Available seats \(availableSeats)") } } queue2.async { Task { let bookedSeat = await flight.bookSeat() print("Booked seat \(bookedSeat)") } } queue3.async { Task { let availableSeats = await flight.getAvailableSeats() print("Available seats after booking \(availableSeats)") } } } }