Swift Concurrency Manifesto | Chris Lattner and Lex Fridman
Ғылым және технология
Lex Fridman Podcast full episode: • Chris Lattner: The Fut...
Please support this podcast by checking out our sponsors:
- Blinkist: blinkist.com/lex and use code LEX to get a free week of premium
- Neuro: www.getneuro.com and use code LEX to get 15% off
- MasterClass: masterclass.com/lex to get 15% off annual sub
- Cash App: cash.app/ and use code LexPodcast to get $10
PODCAST INFO:
Podcast website: lexfridman.com/podcast
Apple Podcasts: apple.co/2lwqZIr
Spotify: spoti.fi/2nEwCF8
RSS: lexfridman.com/feed/podcast/
Full episodes playlist: • Lex Fridman Podcast
Clips playlist: • Lex Fridman Podcast Clips
CONNECT:
- Subscribe to this KZread channel
- Twitter: / lexfridman
- LinkedIn: / lexfridman
- Facebook: / lexfridmanpage
- Instagram: / lexfridman
- Medium: / lexfridman
- Support on Patreon: / lexfridman
Пікірлер: 10
5:38 "You're kind of fu- stuck with a bad set of trade offs" :D
One of my favorite guests
Lex, you are the best!
please make distributed actor compatible with iOS, take in account battery, app lifetime, and bootstrap node by default in in apple
I think my enternet before we apply before last 2018 I thought I finish my contract.
wait, wait, wait........ are you saying you've solved race conditions :0
@jj680l
3 жыл бұрын
Rust language is known to have solved race conditions, even when using shared memory. Not sure about Swift.
@Xaxxus
2 жыл бұрын
@@jj680l yes, as of swift 5.5 race conditions are essentially solved at the compiler level now. Swift added actors. So if you put your race condition prone code into an actor, you will get compile errors when you try to do something that will cause a race condition.
Not excited by async/await. DispatchQueue already has all of these features.
@pawelpow
3 жыл бұрын
Completion handlers? Actors? Synchronous syntax?