Swift编程语言指南中有如下示例:
class Person {
let name: String
init(name: String) { self.name = name }
var apartment: Apartment?
deinit { println("\(name) is being deinitialized") }
}
class Apartment {
let number: Int
init(number: Int) { self.number = number }
var tenant: Person?
deinit { println("Apartment #\(number) is being deinitialized") }
}
var john: Person?
var number73: Apartment?
john = Person(name: "John Appleseed")
number73 = Apartment(number: 73)
//From Apple's “The Swift Programming Language” guide (https://developer.apple.com/library/content/documentation/Swift/Conceptual/Swift_Programming_Language/AutomaticReferenceCounting.html)
然后，在给这个人分配公寓时，他们使用感叹号来“打开实例”:
john!.apartment = number73
“展开实例”是什么意思?为什么有必要?它与仅仅做以下事情有什么不同:
john.apartment = number73
我对Swift语言很不熟悉。我只是想把基本的东西记下来。
更新:
我遗漏了一个很大的谜团(答案中没有直接说明——至少在写这篇文章的时候没有)，那就是当你做以下事情的时候:
var john: Person?
这并不意味着“约翰是人的类型，它可能是nil”，因为我最初的想法。我只是误解了《人与人》是完全不同的类型。一旦我明白了，所有其他的?，!疯狂，以及下面这些精彩的回答，让我觉得更有道理。
John是一个可选的Person，这意味着它可以保存值或为nil。
john.apartment = number73
如果John不是可选选项，则使用。由于john从不为nil，我们可以确定它不会在nil值时调用apartment。而
john!.apartment = number73
向编译器承诺John不是nil，然后打开可选选项以获取John的值并访问John的公寓属性。如果你知道john不是nil就用这个。如果你在可选的nil上调用这个，你会得到一个运行时错误。
文档中包含了一个很好的示例，其中convertedNumber是可选的。
if convertedNumber {
println("\(possibleNumber) has an integer value of \(convertedNumber!)")
} else {
println("\(possibleNumber) could not be converted to an integer")
}
以下是我认为的区别:
var john: Person?
意味着john可以是nil
john?.apartment = number73
编译器将这一行解释为:
if john != nil {
john.apartment = number73
}
而
john!.apartment = number73
编译器将简单地解释这一行:
john.apartment = number73
因此，使用!将打开if语句，并使其运行得更快，但如果John为nil，则会发生运行时错误。
这里的wrap并不是指它是内存包装，而是指它是代码包装，在这种情况下，它是用if语句包装的，因为苹果非常关注运行时的性能，他们想给你一种方法让你的应用以最好的性能运行。
更新:
Getting back to this answer after 4 years, as I got the highest reputations from it in Stackoverflow :)
I misunderstood a little the meaning of unwrapping at that time. Now after 4 years I believe the meaning of unwrapping here is to expand the code from its original compact form. Also it means removing the vagueness around that object, as we are not sure by definition if it is nil or not. Just like the answer of Ashley above, think about it as a present which could contain nothing in it. But I still think that the unwrapping is code unwrapping and not memory based unwrapping as using enum.
