Why you should care about the future of Memory Ownership in Swift