How do safe and unsafe unowned references differ in memory management?

In the context of memory management in Swift, unowned references come in two types: safe and unsafe.

• Safe unowned references are references that assume the object they refer to always exists during access. If the object has been deallocated, attempting to access an unowned reference will cause a runtime error (crash). These references are used when the object's lifecycle is guaranteed to be longer than the reference.

• Unsafe unowned references (for example, UnsafePointer or Unmanaged in Swift) do not check for the existence of the object and do not ensure access safety. They can lead to undefined behavior if the object has been deallocated but the reference is still used.

Example of a safe unowned:

class Owner {
    var child: Child?
}

class Child {
    unowned let owner: Owner
    init(owner: Owner) {
        self.owner = owner
    }
}

Here, child.owner is a safe unowned reference because owner is guaranteed to exist longer than child.

In summary, safe unowned references provide runtime checks and prevent memory leaks without the risk of dangling pointers, while unsafe unowned references do not guarantee safety and require caution when used.