Mind the Memory When Using Value Types
summary
The talk explains Swift’s noncopyable value types introduced in Swift 5.9 and completed with protocol and generic support in Swift 6.0, and shows how to use them to store unique resources without heap allocation or reference semantics. Using an updated Swift and the Ozon Seller project, it demonstrates how noncopyability improves clarity about entity ownership and examines its impact on app performance and memory usage, compares similar approaches in other languages, and discusses potential issues and future solutions.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:32Memory optimization goals
- 6:54Data copy problems
- 12:59Compiler checks B Checker
- 16:50Evolution of non-copyable types
- 20:20Swift new keywords
- 21:46Network request example
- 22:50Data conversion
- 26:23Pagination and UI
- 31:23Modern Concurrency non-copyable types
- 33:10Memory usage metrics
- 37:02Summary and limitations
- 38:53Future of non-copyable types
- 39:15Q&A
