Xcode Setting: Strict Concurrency Checking Complete

Подписаться 16 тыс.

Просмотров 2,2 тыс.

50% 1

In this video we will learn about Strict Concurrency checking type complete and see how it helps us by giving warning about race conditions.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
✅ Subscribe to the channel and stay ahead of everyone by following the right way for writing clean code in swift. 🔥🔥🔥🔥🔥
🔗Click on the link to subscribe: www.youtube.co...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
############################################
Connect with me on social media
Instagram: codecat15
📧: codecat15@gmail.com
🐦: / codecat15
Facebook: / code.cat.792
Github: github.com/cod...
###########################################
#XcodeTips #SwiftConcurrency

Опубликовано:

1 окт 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 18

@alexl7936 Год назад

perfect, short video and straight to the point, thank you!

@CodeCat15 Год назад

Glad this was helpful Alex.

@sanjeevreddy3691 Год назад

If possible pls make video on push notification and app deployment

@RedPPP Год назад

Would using an actor solve the problem? Otherwise a lock has to be used right ?

@CodeCat15 11 месяцев назад

what do you think is the trade-offs of using locks vs actors? which one is better?

@RedPPP 11 месяцев назад

@@CodeCat15 I think Actor is better because it offers an implicit, auto-managed lock. As for Locker, I don't think it currently has an equivalent of Objective-C's lock in Swift, so some self-management is required.

@RedPPP 11 месяцев назад

@@CodeCat15 Trade-off, the actor is new, so not all projects can use it. But, locks are more flexible in terms of implementation and support for legacy codebases.

@venugopalreddy6618 Год назад

Can you please upload a mock interview for junior iOS developer role.

@CodeCat15 11 месяцев назад

I have a question list on medium for the same, also the second link is quite crucial as it has certain points on what you should and shouldn't do in an interview. Interview question: medium.com/swlh/ios-interview-questions-for-beginners-and-experienced-developers-ae067912e038 Master the interview process: codecat15.medium.com/mastering-ios-app-development-interviews-tips-for-success-96702d70d8fd

@venugopalreddy6618 11 месяцев назад

@@CodeCat15 thanks brother

@rohitp9371 11 месяцев назад

We can solve this issue using async await, which will serialize the calls. Also, We can solve this by using a barrier flag, but in that case, we need to mark the class @sendable.

@pradeepkas10 11 месяцев назад

Using dispatch barrier flag in same code

@DmitryKatsubo 11 месяцев назад

Прекрасно, только на этих ваших мега проектах в три строчки кода... На настоящих проектах это будет большая боль )

@rachitsharma8829 11 месяцев назад

Cool.. very useful ❤

@jitendrakumarpradhan2825 Год назад

we can use like this to avoid the diffrent result of sharedValue class ContentViewModel { var sharedVal: Int = 0 let semaphore = DispatchSemaphore(value: 1) // Initialize with a value of 1 func operations() { let concurrentQueue = DispatchQueue(label: "CodeCat15", attributes: .concurrent) concurrentQueue.async { self.semaphore.wait() self.sharedVal = 78 self.semaphore.signal() } concurrentQueue.async { self.semaphore.wait() print(self.sharedVal) self.semaphore.signal() } } }

@CodeCat15 Год назад

Semaphores are good for sure but then they give rise to two issues 1. Deadlocks 2. Priority inversion So the solution could work but there’s a possibility of these two issues that could happen. Can we improve this without using semaphores? There’s a solution for this that I explained in the threading playlist see if you can improvise the solution, you are close to the solution.