Classes were reference-counted automatically, structs and enums were copied freely, and the whole system ran quietly in the background without asking developers to think about ownership at all. Then, starting with Swift 5.9 in 2023, Apple began introducing a set of features, borrowing, consuming, and …
Classes were reference-counted automatically, structs and enums were copied freely, and the whole system ran quietly in the background without asking developers to think about ownership at all.
Then, starting with Swift 5.9 in 2023, Apple began introducing a set of features, borrowing, consuming, and …
For nearly a decade, Swift's relationship to memory looked settled.
The page is ready to read now. The fuller skim-friendly version will appear here automatically.
Classes were reference-counted automatically, structs and enums were copied freely, and the whole system ran quietly in the background without asking developers to think about ownership at all. Then, starting with Swift 5.9 in 2023, Apple began introducing a set of features, borrowing, consuming, and … For nearly a decade, Swift's relationship to memory looked settled.
For nearly a decade, Swift's relationship to memory looked settled.
Open the app view to save this story, compare related coverage, and continue from the same source.