In my code i am displaying the message on tableView in ios swift uikit using actor, the table view delegate methods will call synchronously but the data from actor isolated property i am getting using Task method with in that tableview delegates synchronous execution, now the problem is the tableview delegates method synchronous execution is not waiting for the Task method to wait, can any one suggest on this please
One question, why do we need to mark async for the newMessage method, but do not need to do the same for the history method? Shouldn’t the methods in the actor class be automatically in async context ? Thanks.
Nice Explanation with real time example
Thank you @Salman 😊!
@@swiftandtips it would be great if you put Video on Actor Reentrancy Problem
@@salmansiddiqui9522 Good idea, I will plan that video for later. Thank you! 😁
Great video ! Thank you so much !
Thanks for this complex but clear tutorial in actors demo if have an error: 'Task' cannot be constructed because it has no accessible initializers
Hi @michel, thank you for the comment! ☺️.
Where are you facing that issue? Xcode version?
@@swiftandtips Xcode 13.0 bêta 13a5154h
You should use Xcode 13 beta 3. In the past, it was async { ... }, let me know if that's the issue.
@@swiftandtips Yes it works !
In my code i am displaying the message on tableView in ios swift uikit using actor, the table view delegate methods will call synchronously but the data from actor isolated property i am getting using Task method with in that tableview delegates synchronous execution, now the problem is the tableview delegates method synchronous execution is not waiting for the Task method to wait, can any one suggest on this please
Great tutorial! Nice and clear explanation!
Thank you @Beetroot ☺️!
Do I understand correctly, that all these concurrency issues (data racing etc.) are theoretically possible only if your system has more then one CPU?
This actually could happen in one CPU with concurrent threads too!
Great video!
Thank you @Jalil 😄!
One question, why do we need to mark async for the newMessage method, but do not need to do the same for the history method? Shouldn’t the methods in the actor class be automatically in async context ? Thanks.
Hi David, you are right! That was unnecessary from my end 😅. I discovered that once I finished the recording hehe. Good catch!
@@swiftandtips I see. Thanks for the information. Great video by the way. 😁
Thank you David!
You are the best!!!!
😝😳 Thanks!!