What is the Sendable protocol in Swift? | Swift Concurrency #11

[@bhuwin6186]

bro you are amazing Edit: Also sendable acts as a guard for future safery thread checks, is someone ads a var to a sendable without being aware its being used in asyc sendable will alert them.

[@hashcat5721]

8:41 - In xCode 14.1 there will only be a warning and not an error.

[@taylorchapman7860]

Update: I think in Swift 6 it will become an error, for now just a warning

[@XMunichX]

Thank you as always for your great work Nick!

[@2689742]

Amazing tutorial.Crystal clear.

[@andresraigoza2082]

Awesome as always. Thank you so much!!!

[@piyushagrawal08]

Awesommmmmme Video! Thank you so much fore great video! A huge Salute to you 999999999999 times! Keep sharing your knowledge & making awesome video! genius!

[@josemanuelortizsanchez4983]

Great video, thanks!

[@praveenperera]

Your videos are great, do you have a plan to cover Transferable

[@lalitvinde1441]

hey vro ...how to make Core Data Entities conforming to Sendable??

[@liumingxing3060]

Cool!

[@lincolndickerson1293]

Trying to think of a case that a final class would be needed where a struct or actor couldn’t fit the bill. In the unchecked sendable case shown in the video all we are really doing making an understudy, weak actor, aka an novice implementation of thread safe class? What am I missing?

[@pmjss]

What is the brand of your keyboard that sound is very impress me

[@SwiftfulThinking]

That is a 16” MacBook Pro 😂

[@pmjss]

@@SwiftfulThinking omg 😱

[@alexvaiman4966]

as i said before about mutating.. you must be careful. struct MyStruct: Sendable { var title: String mutating func changeTitle(newTitle: String) { title = newTitle } func unsafe( t: inout MyStruct) { t.changeTitle(newTitle: "new title") } func test() { var t = MyStruct(title: "hello") unsafe(t: &t) print(t.title) } }

[@alexvaiman4966]

This obviously isn't thread-safe.

[@SwiftfulThinking]

@@alexvaiman4966yea I guess I should have been more clear about immutable structs vs mutable structs too

[@alexvaiman4966]

@@SwiftfulThinking Actually, I was wrong. When you try to run a mutating struct function in a thread context, you will get an error saying 'Escaping closure captures mutating 'self' parameter.' So, I guess it is not that structs are thread-safe; they just cannot be shared between threads (which is logical, as most structs are created on the stack). Swift is smart, unlike C++, it will not let you do crazy things.