What is the difference in Swift between 'unowned(safe)' and 'unowned(unsafe)'?

Question

Apple\'s Swift Programming Language Guide mentions the capture specifiers unowned(safe) and unowned(unsafe), in addition to weak

Answer 1

Here is a quote from Apple Developer Forums:

unowned vs unowned(safe) vs unowned(unsafe)

unowned(safe) is a non-owning reference that asserts on access that the object is still alive. It's sort of like a weak optional reference that's implicitly unwrapped with x! every time it's accessed. unowned(unsafe) is like __unsafe_unretained in ARC—it's a non-owning reference, but there's no runtime check that the object is still alive on access, so dangling references will reach into garbage memory. unowned is always a synonym for unowned(safe) currently, but the intent is that it will be optimized to unowned(unsafe) in -Ofast builds when runtime checks are disabled.