@@iOSAcademy And include all the nested network calls . like populating a table view with users, their photos, etc all separate calls, proper error handling , etc. all the pain-in-the-ass stuff. Just my $.02. regards and keep up the great work
The syntax is much better, it makes sense. completion handlers didn't make sense as they are part of the function parameters but when you call them, the closure is outside the params ().
Well, no they don't have to be at all. You can certainly put a closure inside the function parenthesis. What you are talking about is a trailing closure syntax, which is only if you have a closure that is the last argument of the function. You don't have to use trailing closure syntax if you don't want to.
I wish these tutorials were done in SwiftUI, much cleaner, and much faster. Instead of spending like 8 minutes setting up the project due to UIkit nonsense, just add List (user) and be done.
can you or someone please tell me what is the different of the tableview variable you wrote that looks the same as lazy variable definition, but without the lazy keyword. is it behave like lazy? is this variable create only once and only when someone access to it? at 03:55
But what if we are using alamofire which returns a Result type data, from which it’s not possible to return data as we can’t return anything inside cases of result, how to handle that any help would be appreciated.
how did you do that without adding import _Concurrency? I get error about couldn't found async. Also imported concurrency but couldn't found that module.
We all know async calls do not block execution until the async operation is completed. With await being introduced are we still doing that or are we waiting on the async operation being completed?
setting users property in 8:54 should also happen on main thread. Does "async" in line 31 dispatch closure on current thread? that would make DispatchQueue.main.asynch from line 35 unneccesary.
@@MrLinusunil You can if you use some kind of synchronization. Otherwise you have potential data race or inconsistent state because two threads are accessing the same property, one changing it. For example: property is read on main thread in table view data source method numberOfRows, then propeerty is changed on non-main thread before cellForRowAt call, then you have crash "index out of range".
Man that so fast, it doesn't take a week and you already make tutorial for new features. Keep going bro!
Thanks, will do!
Nice. I think a whole series of tutorials on this is needed, with simple to complex use cases. I would buy the course if you made one :)
Coming soon!
@@iOSAcademy And include all the nested network calls . like populating a table view with users, their photos, etc all separate calls, proper error handling , etc. all the pain-in-the-ass stuff. Just my $.02. regards and keep up the great work
@@iOSAcademy any ETA on this?
These videos are absolutely outstanding summaries thank you 🙏
Thanks
You saved my life.
Great! simply great, thanks!!
You’re welcome
Some imminent deprecation on the "async { ... }" call. Need to change it (going forward) to "Task { ... } "
Yep
can be use Task instead of async for concurrent or parallel proccesing?
good job! thanks mate!
Youre welcome
Great video. I'm a senior iOS engineer but trying to catch up on some APIs I've been lazy to learn.
Nice!
same
Easy to understand 👏🏻
Thanks
Beautiful video. Bravo!
Thanks
yeah ima call you professor iOS now
haha thanks!
async {} is now Task.init(operation: {})
Or just "Task { }" - which is the same thing. You don't have to use init and the only argument can be done with a trailing closure.
They are making it easy.
Yep!
Simple and clear, thanks mate!
Youre welcome
Nice, looking forward to some practice about it
Nice
Thank you for the great explanation
The syntax is much better, it makes sense. completion handlers didn't make sense as they are part of the function parameters but when you call them, the closure is outside the params ().
Well, no they don't have to be at all. You can certainly put a closure inside the function parenthesis. What you are talking about is a trailing closure syntax, which is only if you have a closure that is the last argument of the function. You don't have to use trailing closure syntax if you don't want to.
Really good video, thanks for sharing that. It was concise and easy to understand.
Thanks
if use Task what would happen?
I wish these tutorials were done in SwiftUI, much cleaner, and much faster. Instead of spending like 8 minutes setting up the project due to UIkit nonsense, just add List (user) and be done.
can you or someone please tell me what is the different of the tableview variable you wrote that looks the same as lazy variable definition, but without the lazy keyword.
is it behave like lazy? is this variable create only once and only when someone access to it?
at 03:55
But what if we are using alamofire which returns a Result type data, from which it’s not possible to return data as we can’t return anything inside cases of result, how to handle that any help would be appreciated.
Is concurrency is async?
Yes
Thanks for the content, btw which theme in Xcode do you use?
Midnight
how did you do that without adding import _Concurrency? I get error about couldn't found async. Also imported concurrency but couldn't found that module.
It should work in xcode 13
so is @escaping completion handlers obsolete now?
No. Both are still valid
@@iOSAcademy but its possible to replace the completion Blocks with it, right?
from javascript
Literally lol
Yep!
I know right ? What took so long ??? Apple is a $2T company.
Async await it's pretty cool and very simple ❤️. Thank you for u tutorial sir. Please, if is possible, make a tutorial about repository sir. 😁
Sure I will
Do you have a video on how to use a REST API with Swift?
Yes, just search for API on the channel
@@iOSAcademy Great!
We all know async calls do not block execution until the async operation is completed.
With await being introduced are we still doing that or are we waiting on the async operation being completed?
Waiting
@@iOSAcademy Got it. So anything that we do NOT want to wait for async call should be outside the "Task" block?
Bad quality of the video. Please fix this. You hurt our eyes. Besides that, thanks for the content. It's very helpful.
You wasted almost half the video setting up the project before showing the concept. Next time, have the project already prepared.
I think the weak self attempt was correct.
async { [weak self] in
guard let _self = self else {
return
}
let users = await fetchUsers()
_self.users = users
DispatchQueue.main.async {
_self.tableView.reloadData()
}
}
🙃
As of Swift 5, you can use "let self = self "
setting users property in 8:54 should also happen on main thread. Does "async" in line 31 dispatch closure on current thread? that would make DispatchQueue.main.asynch from line 35 unneccesary.
AFAIK you can perfectly do that on non-main threads. Only updating the UI (like reloading the table view) needs to be on the main thread.
@@MrLinusunil You can if you use some kind of synchronization.
Otherwise you have potential data race or inconsistent state because two threads are accessing the same property, one changing it.
For example: property is read on main thread in table view data source method numberOfRows,
then propeerty is changed on non-main thread before cellForRowAt call, then you have crash "index out of range".