Swift Style Guide

Swift代碼規范指南

Make sure to read Apple's API Design Guidelines.
確保閱讀蘋果的API設計指南。

Specifics from these guidelines + additional remarks are mentioned below.
下文提到了這些指南中的具體細節+補充意見。

This guide was last updated for Swift 4.0 on February 14, 2018.
本指南最后一次針對Swift 4.0更新是在2018年2月14日。

Swift Style Guide
Swift代碼規范指南
- 1. Code Formatting
- 1. 代碼格式
- 1. Naming
- 1. 命名
- 1. Coding Style
- 1. 編碼規范
  - 3.1 General
  - 3.1 概述
  - 3.2 Access Modifiers
  - 3.2 訪問修飾符
  - 3.3 Custom Operators
  - 3.3 自定義操作符
  - 3.4 Switch Statements and enums
  - 3.4 Switch語句和枚舉
  - 3.5 Optionals
  - 3.5 可選類型
  - 3.6 Protocols
  - 3.6 協議
  - 3.7 Properties
  - 3.7 屬性
  - 3.8 Closures
  - 3.8 閉包
  - 3.9 Arrays
  - 3.9 數組
  - 3.10 Error Handling
  - 3.10 錯誤處理
  - 3.11 Using guard Statements
  - 3.11 使用 guard 語句
- 1. Documentation/Comments
- 1. 文檔/注釋
  - 4.1 Documentation
  - 4.1 文檔
  - 4.2 Other Commenting Guidelines
  - 4.2 其他注釋原則

1. Code Formatting

1. 代碼格式

1.1 Use 4 spaces for tabs.
1.1 使用四個空格進行縮進。
1.2 Avoid uncomfortably long lines with a hard maximum of 160 characters per line (Xcode->Preferences->Text Editing->Page guide at column: 160 is helpful for this)
1.2 每行最多160個字符，這樣可以避免一行過長 (Xcode->Preferences->Text Editing->Page guide at column: 設置成160行即可)

譯者注：大可不必設置，自己API設計好一點即可，調用他人的API也無法避免行數過長，真的超了設置也起不了什么作用，再說Xcode本身有自動換行。

1.3 Ensure that there is a newline at the end of every file.
1.3 確保每個文件結尾都有空白行。

譯者注：Xcode12開始，每個文件結尾都自動有偏移量了，開發者自己不必加空行。

1.4 Ensure that there is no trailing whitespace anywhere (Xcode->Preferences->Text Editing->Automatically trim trailing whitespace + Including whitespace-only lines).
1.4 確保每行都不以空白字符作為結尾（Xcode->Preferences->Text Editing->Automatically trim trailing whitespace + Including whitespace-only lines)。

譯者注：這樣能避免修改代碼過程中因多個空格、少個空格而產生不必要的文件差異。如果項目里的每個開發人員都設置最好，否則只要有人不設置，他提交的代碼還是會出現結尾有空白字符，而其他設置過的人觸碰到該行代碼，空格自動消失，產生的差異還無法回退。

1.5 Do not place opening braces on new lines - we use the 1TBS style.
1.5 左大括號不用另起一行。

class SomeClass {
    func someMethod() {
        if x == y {
            /* ... */
        } else if x == z {
            /* ... */
        } else {
            /* ... */
        }
    }

    /* ... */
}

1.6 When writing a type for a property, constant, variable, a key for a dictionary, a function argument, a protocol conformance, or a superclass, don't add a space before the colon.
1.6 當在寫一個變量類型，一個字典里的主鍵，一個函數的參數，遵從一個協議，或一個父類，不用在分號前添加空格。

// specifying type
let pirateViewController: PirateViewController

// dictionary syntax (note that we left-align as opposed to aligning colons)
let ninjaDictionary: [String: AnyObject] = [
    "fightLikeDairyFarmer": false,
    "disgusting": true
]

// declaring a function
func myFunction<T, U: SomeProtocol>(firstArgument: U, secondArgument: T) where T.RelatedType == U {
    /* ... */
}

// calling a function
someFunction(someArgument: "Kitten")

// superclasses
class PirateViewController: UIViewController {
    /* ... */
}

// protocols
extension PirateViewController: UITableViewDataSource {
    /* ... */
}

1.7 In general, there should be a space following a comma.
1.7 通常來說，要在逗號后面加空格。

let myArray = [1, 2, 3, 4, 5]

1.8 There should be a space before and after a binary operator such as +, ==, or ->. There should also not be a space after a ( and before a ).
1.8 在二元運算符前后要加空格，例如+, ==, 或 ->。而在左括號( 后面和有括號)的前面不要加空格。

let myValue = 20 + (30 / 2) * 3
if 1 + 1 == 3 {
    fatalError("The universe is broken.")
}
func pancake(with syrup: Syrup) -> Pancake {
    /* ... */
}

1.9 We follow Xcode's recommended indentation style (i.e. your code should not change if CTRL-I is pressed). When declaring a function that spans multiple lines, prefer using that syntax to which Xcode, as of version 7.3, defaults.
1.9 遵守Xcode內置的縮進格式 (如果已經遵守，按下Control+i鍵，代碼格式不會有變化). 當聲明的一個函數需要跨多行時，推薦使用Xcode默認的格式，目前Xcode 版本是 7.3。

// Xcode indentation for a function declaration that spans multiple lines
func myFunctionWithManyParameters(parameterOne: String,
                                  parameterTwo: String,
                                  parameterThree: String) {
    // Xcode indents to here for this kind of statement
    print("\(parameterOne) \(parameterTwo) \(parameterThree)")
}

// Xcode indentation for a multi-line `if` statement
if myFirstValue > (mySecondValue + myThirdValue)
    && myFourthValue == .someEnumValue {

    // Xcode indents to here for this kind of statement
    print("Hello, World!")
}

1.10 When calling a function that has many parameters, put each argument on a separate line with a single extra indentation.
1.10 當調用的函數有多個參數時，每一個參數另起一行，并比函數名多一個縮進。

someFunctionWithManyArguments(
    firstArgument: "Hello, I am a string",
    secondArgument: resultFromSomeFunction(),
    thirdArgument: someOtherLocalProperty)

譯者注：其實我個人不建議參數換行，除非參數需要突出讓閱讀者注意，否則適得其反，總之慎用！慎用！慎用！
很多開發者不僅喜歡參數換行，并且第一個參數不換行，格式對齊后，整個代碼塊擠在了右邊一小塊，凌亂不堪，閱讀起來真難受。

什么鬼？這種代碼都寫得出...

所有參數都換行，比上面好看很多。

個人更傾向于不換行，縱向閱讀容易理解這里主要就兩句代碼，一是獲取股票持倉者，通過閉包回調，二是閉包內處理回調數據。
有必要的情況下可以使用參數換行，但一定不要出現第一張圖那種凌亂不堪的代碼。

1.11 When dealing with an implicit array or dictionary large enough to warrant splitting it into multiple lines, treat the [ and ] as if they were braces in a method, if statement, etc. Closures in a method should be treated similarly.
1.11 當遇到需要處理的數組或字典內容較多需要多行顯示時，需把 [ 和 ] 類似于方法體里的括號，方法體里的閉包也要做類似處理。

someFunctionWithABunchOfArguments(
    someStringArgument: "hello I am a string",
    someArrayArgument: [
        "dadada daaaa daaaa dadada daaaa daaaa dadada daaaa daaaa",
        "string one is crazy - what is it thinking?"
    ],
    someDictionaryArgument: [
        "dictionary key 1": "some value 1, but also some more text here",
        "dictionary key 2": "some value 2"
    ],
    someClosure: { parameter1 in
        print(parameter1)
    })

1.12 Prefer using local constants or other mitigation techniques to avoid multi-line predicates where possible.
1.12 應盡量避免出現多行斷言，可使用本地變量或其他策略。

// PREFERRED
let firstCondition = x == firstReallyReallyLongPredicateFunction()
let secondCondition = y == secondReallyReallyLongPredicateFunction()
let thirdCondition = z == thirdReallyReallyLongPredicateFunction()
if firstCondition && secondCondition && thirdCondition {
    // do something
}

// NOT PREFERRED
if x == firstReallyReallyLongPredicateFunction()
    && y == secondReallyReallyLongPredicateFunction()
    && z == thirdReallyReallyLongPredicateFunction() {
    // do something
}

2. Naming

2. 命名

2.1 There is no need for Objective-C style prefixing in Swift (e.g. use just GuybrushThreepwood instead of LIGuybrushThreepwood).
2.1 在Swift中不用如Objective-C式一樣添加前綴 (如使用 GuybrushThreepwoode 而不是 LIGuybrushThreepwood)。

譯者注：還是有很多人寫Swift習慣用前綴，那是因為沒有明白Swift的真諦，Swift不同框架即便用同個類名也不會沖突，在同一個文件中使用到二者，需要引用對應框架名來區分。

2.2 Use PascalCase for type names (e.g. struct, enum, class, typedef, associatedtype, etc.).
2.2 使用帕斯卡拼寫法（又名大駱駝拼寫法，首字母大寫）為類型命名 (如 struct, enum, class, typedef, associatedtype 等)。
2.3 Use camelCase (initial lowercase letter) for function, method, property, constant, variable, argument names, enum cases, etc.
2.3 使用小駱駝拼寫法 (首字母小寫) 為函數，方法，變量，常量，參數等命名。
2.4 When dealing with an acronym or other name that is usually written in all caps, actually use all caps in any names that use this in code. The exception is if this word is at the start of a name that needs to start with lowercase - in this case, use all lowercase for the acronym.
2.4 首字母縮略詞在命名中一般來說都是全部大寫，例外的情形是如果首字母縮略詞是一個命名的開始部分，而這個命名需要小寫字母作為開頭，這種情形下首字母縮略詞全部小寫。

// "HTML" is at the start of a constant name, so we use lowercase "html"
let htmlBodyContent: String = "<p>Hello, World!</p>"
// Prefer using ID to Id
let profileID: Int = 1
// Prefer URLFinder to UrlFinder
class URLFinder {
    /* ... */
}

2.5 All constants that are instance-independent should be static. All such static constants should be placed in a marked section of their class, struct, or enum. For classes with many constants, you should group constants that have similar or the same prefixes, suffixes and/or use cases.
2.5 所有與實例無關的常量都應該是static。所有這些static常數都應放置在其class、struct或enum的標記部分。對于具有許多常量的類，您應該對具有相似或相同前綴、后綴和/或用例的常量進行分組。

// PREFERRED    
class MyClassName {
    // MARK: - Constants
    static let buttonPadding: CGFloat = 20.0
    static let indianaPi = 3
    static let shared = MyClassName()
}

// NOT PREFERRED
class MyClassName {
    // Don't use `k`-prefix
    static let kButtonPadding: CGFloat = 20.0

    // Don't namespace constants
    enum Constant {
        static let indianaPi = 3
    }
}

譯者注：蘋果代碼規范指南里每一點都有其意義及精髓存在，需要用心去體會其設計意義。否則每個人都按自己的方式，或者沿用其他語言的習慣來寫，代碼將風格迥異。我甚至看到有一篇譯文，枉顧蘋果的代碼示例，固執己見推薦使用k作為前綴。k作為前綴是OC的宏定義的寫法，在Swift中不推薦這種寫法。

2.6 For generics and associated types, use a PascalCase word that describes the generic. If this word clashes with a protocol that it conforms to or a superclass that it subclasses, you can append a Type suffix to the associated type or generic name.
2.6 對于泛型和相關類型，請使用PascalCase單詞（大駝峰式命名）描述泛型。如果此詞與其遵循的協議名或繼承類的超類名沖突，您可以在關聯類型或泛型名稱中添加Type后綴。

class SomeClass<Model> { /* ... */ }
protocol Modelable {
    associatedtype Model
}
protocol Sequence {
    associatedtype IteratorType: Iterator
}

2.7 Names should be descriptive and unambiguous.
2.7 姓名應具有描述性和明確性。

// PREFERRED
class RoundAnimatingButton: UIButton { /* ... */ }

// NOT PREFERRED
class CustomButton: UIButton { /* ... */ }

2.8 Do not abbreviate, use shortened names, or single letter names.
2.8 不要縮寫、簡寫命名或用單個字母命名。

// PREFERRED
class RoundAnimatingButton: UIButton {
    let animationDuration: NSTimeInterval

    func startAnimating() {
        let firstSubview = subviews.first
    }

}

// NOT PREFERRED
class RoundAnimating: UIButton {
    let aniDur: NSTimeInterval

    func srtAnmating() {
        let v = subviews.first
    }
}

2.9 Include type information in constant or variable names when it is not obvious otherwise.
2.9 當常量或變量名稱不能明顯地表明類型時，應當將類型信息包含在命名中。

// PREFERRED
class ConnectionTableViewCell: UITableViewCell {
    let personImageView: UIImageView

    let animationDuration: TimeInterval

    // it is ok not to include string in the ivar name here because it's obvious
    // that it's a string from the property name
    let firstName: String

    // though not preferred, it is OK to use `Controller` instead of `ViewController`
    let popupController: UIViewController
    let popupViewController: UIViewController

    // when working with a subclass of `UIViewController` such as a table view
    // controller, collection view controller, split view controller, etc.,
    // fully indicate the type in the name.
    let popupTableViewController: UITableViewController

    // when working with outlets, make sure to specify the outlet type in the
    // property name.
    @IBOutlet weak var submitButton: UIButton!
    @IBOutlet weak var emailTextField: UITextField!
    @IBOutlet weak var nameLabel: UILabel!

}

// NOT PREFERRED
class ConnectionTableViewCell: UITableViewCell {
    // this isn't a `UIImage`, so shouldn't be called image
    // use personImageView instead
    let personImage: UIImageView

    // this isn't a `String`, so it should be `textLabel`
    let text: UILabel

    // `animation` is not clearly a time interval
    // use `animationDuration` or `animationTimeInterval` instead
    let animation: TimeInterval

    // this is not obviously a `String`
    // use `transitionText` or `transitionString` instead
    let transition: String

    // this is a view controller - not a view
    let popupView: UIViewController

    // as mentioned previously, we don't want to use abbreviations, so don't use
    // `VC` instead of `ViewController`
    let popupVC: UIViewController

    // even though this is still technically a `UIViewController`, this property
    // should indicate that we are working with a *Table* View Controller
    let popupViewController: UITableViewController

    // for the sake of consistency, we should put the type name at the end of the
    // property name and not at the start
    @IBOutlet weak var btnSubmit: UIButton!
    @IBOutlet weak var buttonSubmit: UIButton!

    // we should always have a type in the property name when dealing with outlets
    // for example, here, we should have `firstNameLabel` instead
    @IBOutlet weak var firstName: UILabel!
}

譯者注：許多開發人員在屬性命名方面真的很隨意，也不學學蘋果系統框架中是怎么命名的，讓其他開發閱讀起來有多累！

2.10 When naming function arguments, make sure that the function can be read easily to understand the purpose of each argument.
2.10 命名函數參數時，請確保函數易于閱讀以理解每個參數的用途。
2.11 As per Apple's API Design Guidelines, a protocol should be named as nouns if they describe what something is doing (e.g. Collection) and using the suffixes able, ible, or ing if it describes a capability (e.g. Equatable, ProgressReporting). If neither of those options makes sense for your use case, you can add a Protocol suffix to the protocol's name as well. Some example protocols are below.
2.11 根據蘋果的API設計指南，如果protocol描述了正在做的事情（例如Collection）并使用后綴able、ible或ing如果它描述了一種功能（例如Equatable，ProgressReporting）。如果這兩個選項對您的用例都毫無意義，您也可以在協議名稱中添加協議后綴。以下是一些協議示例。

// here, the name is a noun that describes what the protocol does
protocol TableViewSectionProvider {
    func rowHeight(at row: Int) -> CGFloat
    var numberOfRows: Int { get }
    /* ... */
}

// here, the protocol is a capability, and we name it appropriately
protocol Loggable {
    func logCurrentState()
    /* ... */
}

// suppose we have an `InputTextView` class, but we also want a protocol
// to generalize some of the functionality - it might be appropriate to
// use the `Protocol` suffix here
protocol InputTextViewProtocol {
    func sendTrackingEvent()
    func inputText() -> String
    /* ... */
}

3. Coding Style

3. 編碼風格

3.1 General

3.1 概述

3.1.1 Prefer let to var whenever possible.
3.1.1 盡可能使用let（能用let就不要用var）
3.1.2 Prefer the composition of map, filter, reduce, etc. over iterating when transforming from one collection to another. Make sure to avoid using closures that have side effects when using these methods.
3.1.2 從一個集合轉換為另一個集合時，推薦使用map、filter、reduce等。從一個集合轉換到另一個集合時過度迭代。使用這些方法時，請確保避免使用有副作用的閉包。

// PREFERRED
let stringOfInts = [1, 2, 3].flatMap { String($0) }
// ["1", "2", "3"]

// NOT PREFERRED
var stringOfInts: [String] = []
for integer in [1, 2, 3] {
    stringOfInts.append(String(integer))
}

// PREFERRED
let evenNumbers = [4, 8, 15, 16, 23, 42].filter { $0 % 2 == 0 }
// [4, 8, 16, 42]

// NOT PREFERRED
var evenNumbers: [Int] = []
for integer in [4, 8, 15, 16, 23, 42] {
    if integer % 2 == 0 {
        evenNumbers.append(integer)
    }
}

3.1.3 Prefer not declaring types for constants or variables if they can be inferred anyway.
3.1.3 如果可以推斷出常量或變量類型，最好不要聲明它們的類型。

// 推薦
let url = "xxx"
let port = 8080

// 不推薦
let url: String = "xxx"
let port: Int = 8080

3.1.4 If a function returns multiple values, prefer returning a tuple to using inout arguments (it’s best to use labeled tuples for clarity on what you’re returning if it is not otherwise obvious). If you use a certain tuple more than once, consider using a typealias. If you’re returning 3 or more items in a tuple, consider using a struct or class instead.
3.1.4 如果函數返回多個值，傾向于返回元組，而不是使用inout參數（如果元組的項的含義不明顯，最好使用帶標簽的元組來明確要返回的內容）。如果您多次使用某個元組，請考慮使用typealias。如果您要以元組返回3個或更多項目，請考慮改用struct或class。

func pirateName() -> (firstName: String, lastName: String) {
    return ("Guybrush", "Threepwood")
}

let name = pirateName()
let firstName = name.firstName
let lastName = name.lastName

3.1.5 Be wary of retain cycles when creating delegates/protocols for your classes; typically, these properties should be declared weak.
3.1.5 為類創建委托/協議時，請小心保留周期；通常，這些屬性應聲明為weak。
3.1.6 Be careful when calling self directly from an escaping closure as this can cause a retain cycle - use a capture list when this might be the case:
3.1.6 直接從轉義閉包調用self時要小心，因為這可能導致保留循環 - 在這種情況下使用捕獲列表：

myFunctionWithEscapingClosure() { [weak self] (error) -> Void in
    // you can do this

    self?.doSomething()

    // or you can do this

    guard let strongSelf = self else {
        return
    }

    strongSelf.doSomething()
}

譯者注：Swift4.2之后建議這么寫 guard let self = self else { return }
見：https://github.com/apple/swift-evolution/blob/master/proposals/0079-upgrade-self-from-weak-to-strong.md#relying-on-a-compiler-bug

3.1.7 Don't use labeled breaks.
3.1.7 Switch 模塊中不用顯式使用break。
3.1.8 Don't place parentheses around control flow predicates.
3.1.8 控制流斷言不用加小括號。

// PREFERRED
if x == y {
    /* ... */
}

// NOT PREFERRED
if (x == y) {
    /* ... */
}

3.1.9 Avoid writing out an enum type where possible - use shorthand.
3.1.9 使用枚舉時，盡可能不要把類型寫出來。

// PREFERRED
imageView.setImageWithURL(url, type: .person)

// NOT PREFERRED
imageView.setImageWithURL(url, type: AsyncImageView.Type.person)

3.1.10 Don’t use shorthand for class methods since it is generally more difficult to infer the context from class methods as opposed to enums.
3.1.10 不要對類方法使用簡寫，因為從類方法推斷上下文通常比枚舉更難。

// PREFERRED
imageView.backgroundColor = UIColor.white

// NOT PREFERRED
imageView.backgroundColor = .white

譯者注：這里我覺得UIColor類方法簡寫還是能使代碼更簡潔的，我習慣簡寫，但其他類方法還是看具體而定，如果簡寫不能很好地推斷上下文，那還是建議加上類名為好。

3.1.11 Prefer not writing self. unless it is required.
3.1.11 盡量不要使用self.，除非必要（閉包內必須使用self.）。
3.1.12 When writing methods, keep in mind whether the method is intended to be overridden or not. If not, mark it as final, though keep in mind that this will prevent the method from being overwritten for testing purposes. In general, final methods result in improved compilation times, so it is good to use this when applicable. Be particularly careful, however, when applying the final keyword in a library since it is non-trivial to change something to be non-final in a library as opposed to have changing something to be non-final in your local project.
3.1.12 在編寫方法時，需要衡量該方法是否將來會被重寫，如果不希望被子類重寫，請使用final關鍵詞修飾。一般來說，final修飾的方法可以得到編譯速度的優化，在有必要時，使用final是不錯的選擇。但特別要注意的是，相比在本地項目來說，在庫中將final改為非final并非易事。
3.1.13 When using a statement such as else, catch, etc. that follows a block, put this keyword on the same line as the block. Again, we are following the 1TBS style here. Example if/else and do/catch code is below.
3.1.13 在代碼塊后面使用else, catch等語句時，將關鍵詞與代碼塊放在同一行。我們在這里遵循 1TBS style。下面有if/else and do/catch的示例。

if someBoolean {
    // do something
} else {
    // do something else
}

do {
    let fileContents = try readFile("filename.txt")
} catch {
    print(error)
}

3.1.14 Prefer static to class when declaring a function or property that is associated with a class as opposed to an instance of that class. Only use class if you specifically need the functionality of overriding that function or property in a subclass, though consider using a protocol to achieve this instead.
3.1.14 在聲明與類相關聯的函數或屬性而不是該類的實例時，優先使用 static 而非 class。僅當您特別需要在子類中覆蓋該函數或屬性的功能時才使用 class，盡管考慮使用 protocol 來實現這一點。
3.1.15 If you have a function that takes no arguments, has no side effects, and returns some object or value, prefer using a computed property instead.
3.1.15 如果您的函數沒有參數，沒有副作用，并返回一些對象或值，則更喜歡使用計算屬性。

譯者注：這里要好好理解副作用的意思，是指一些不應該有的，或讓人意料之外的作用。下面我列舉一些代碼示例。

// 推薦
struct Square {
    var side: CGFloat = 1.0
    // 獲取周長，使用計算屬性
    var girth: CGFloat {
        return side * 4
    }
}
// 不推薦
struct Square {
    var side: CGFloat = 1.0
    // 無參數、無`副作用`，返回周長，不推薦使用函數
    func girth() -> CGFloat {
        return side * 4
    }
}

// 推薦
class Square {
    var side: CGFloat = 1.0
    // 將邊長縮小一半，并返回縮小后的周長，使用函數
    func halfGirth() -> CGFloat {
        self.side = side * 0.5
        return side * 4
    }
}
// 不推薦
class Square {
    var side: CGFloat = 1.0
    // 這里存在`副作用`，讓人意想不到，不推薦使用計算屬性
    var halfGirth: CGFloat {
        self.side = side * 0.5
        return side * 4
    }
}

3.2 Access Modifiers

3.2 訪問修飾符

3.2.1 Write the access modifier keyword first if it is needed.
3.2.1 如果需要，將訪問修飾符放在第一位。

// PREFERRED
private static let myPrivateNumber: Int

// NOT PREFERRED
static private let myPrivateNumber: Int

3.2.2 The access modifier keyword should not be on a line by itself - keep it inline with what it is describing.
3.2.2 訪問修飾符不應單獨成行，應與修飾的內容放在同一行。

// PREFERRED
open class Pirate {
    /* ... */
}

// NOT PREFERRED
open
class Pirate {
    /* ... */
}

3.2.3 In general, do not write the internal access modifier keyword since it is the default.
3.2.3 一般來說，不要編寫internal訪問修飾符關鍵字，因為它是默認的。
3.2.4 If a property needs to be accessed by unit tests, you will have to make it internal to use @testable import ModuleName. If a property should be private, but you declare it to be internal for the purposes of unit testing, make sure you add an appropriate bit of documentation commenting that explains this. You can make use of the - warning: markup syntax for clarity as shown below.
3.2.4 如果需要通過單元測試訪問屬性，在單元測試文件中使用@testable import ModuleName，以此來訪問聲明為internal的類型。如果一個屬性應該是private的，但為了單元測試的目的，您聲明它是internal的，請確保添加適當的文檔注釋來解釋這一點。您可以使用- warning:標記語法來保持清晰，如下所示。

/**
 This property defines the pirate's name.
 - warning: Not `private` for `@testable`.
 */
let pirateName = "LeChuck"

3.2.5 Prefer private to fileprivate where possible.
3.2.5 能用private的，就不要用fileprivate。
3.2.6 When choosing between public and open, prefer open if you intend for something to be subclassable outside of a given module and public otherwise. Note that anything internal and above can be subclassed in tests by using @testable import, so this shouldn't be a reason to use open. In general, lean towards being a bit more liberal with using open when it comes to libraries, but a bit more conservative when it comes to modules in a codebase such as an app where it is easy to change things in multiple modules simultaneously.
3.2.6 在public和open之間怎么選擇？如果您打算將某些東西在給定模塊之外進行子類化時，使用open，否則使用public。請注意，任何internal或以上級別的內容，在單元測試中都可以通過@testable import來使用，無需將其聲明為open。一般來說，在庫方面，傾向于更自由地使用open，但像app這種可以輕松地同時修改多個模塊的模塊中，則傾向于更保守一點。

3.3 Custom Operators

3.3 自定義操作符

Prefer creating named functions to custom operators.
不推薦使用自定義操作符，如果需要創建函數來替代。

If you want to introduce a custom operator, make sure that you have a very good reason why you want to introduce a new operator into global scope as opposed to using some other construct.
如果您想引入自定義運算符，請確保您有很好的理由，為什么您希望將新運算符引入全局范圍，而不使用其他構造。

You can override existing operators to support new types (especially ==). However, your new definitions must preserve the semantics of the operator. For example, == must always test equality and return a boolean.
您可以重寫已存在的運算符來支持新的類型（特別是==），但無論如何，你都得保留運算符原來的語義，例如，==必須是用來測試是否相等并返回布爾值。

譯者注：相信很多人也不會去重寫運算符，更多的是使用自定義方法，反正不要去踩這個坑。

3.4 Switch Statements and `enum`s

3.4 Switch語句和`enum`

3.4.1 When using a switch statement that has a finite set of possibilities (enum), do NOT include a default case. Instead, place unused cases at the bottom and use the break keyword to prevent execution.
3.4.1 使用有限集合（enum）的switch語句時，不要包含default。反之，switch語句的末尾用default涵蓋其他情況。
3.4.2 Since switch cases in Swift break by default, do not include the break keyword if it is not needed.
3.4.2 switch語句在Swift中默認是會break的，因此不需要添加break（OC中需要在每個case末尾添加break）。
3.4.3 The case statements should line up with the switch statement itself as per default Swift standards.
3.4.3 根據默認Swift標準，case語句應與switch本身對齊。
3.4.4 When defining a case that has an associated value, make sure that this value is appropriately labeled as opposed to just types (e.g. case hunger(hungerLevel: Int) instead of case hunger(Int)).
3.4.4 在定義有關聯值的case時，請確保該值有恰當的名稱，而不只有類型（例如，case hunger(hungerLevel: Int)而不是case hunger(Int)）。

enum Problem {
    case attitude
    case hair
    case hunger(hungerLevel: Int)
}

func handleProblem(problem: Problem) {
    switch problem {
    case .attitude:
        print("At least I don't have a hair problem.")
    case .hair:
        print("Your barber didn't know when to stop.")
    case .hunger(let hungerLevel):
        print("The hunger level is \(hungerLevel).")
    }
}

3.4.5 Prefer lists of possibilities (e.g. case 1, 2, 3:) to using the fallthrough keyword where possible).
3.4.5 推薦使用多個可能性（例如case 1, 2, 3:），而不用fallthrough。
3.4.6 If you have a default case that shouldn't be reached, preferably throw an error (or handle it some other similar way such as asserting).
3.4.6 如果default的情況不應該被觸發，最好拋出錯誤（或以其他類似方式處理它，例如斷言）。

func handleDigit(_ digit: Int) throws {
    switch digit {
    case 0, 1, 2, 3, 4, 5, 6, 7, 8, 9:
        print("Yes, \(digit) is a digit!")
    default:
        throw Error(message: "The given number was not a digit.")
    }
}

3.5 Optionals

3.5 可選

3.5.1 The only time you should be using implicitly unwrapped optionals is with @IBOutlets. In every other case, it is better to use a non-optional or regular optional property. Yes, there are cases in which you can probably "guarantee" that the property will never be nil when used, but it is better to be safe and consistent. Similarly, don't use force unwraps.
3.5.1 唯一應該使用隱式解包可選類型的場景是與@IBOutlet結合使用。在所有其他情況下，最好使用非可選或顯式可選屬性（這樣可以保持一致性和程序更加健壯）。雖然在某些情況下，您可能可以“保證”屬性在使用時永遠不會為nil，但最好是安全和一致。同樣，不要強制解包。
3.5.2 Don't use as! or try!.
3.5.2 不要使用as! 或 try!
3.5.3 If you don't plan on actually using the value stored in an optional, but need to determine whether or not this value is nil, explicitly check this value against nil as opposed to using if let syntax.
3.5.3 如果您不打算可選類型中存儲的值，只是需要判斷值是否為nil，應直接將其與nil比較，而不是使用if let語法。

// PREFERRED
if someOptional != nil {
    // do something
}

// NOT PREFERRED
if let _ = someOptional {
    // do something
}

3.5.4 Don't use unowned. You can think of unowned as somewhat of an equivalent of a weak property that is implicitly unwrapped (though unowned has slight performance improvements on account of completely ignoring reference counting). Since we don't ever want to have implicit unwraps, we similarly don't want unowned properties.
3.5.4 不要使用unowned。您可以將unowned屬性看做是一個強制解包的weak屬性（盡管unowned是完全忽略引用計數，性能略有提升）。由于我們不推薦強制解包，因此同樣不推薦使用unowned屬性。

// PREFERRED
weak var parentViewController: UIViewController?

// NOT PREFERRED
weak var parentViewController: UIViewController!
unowned var parentViewController: UIViewController

3.5.5 When unwrapping optionals, use the same name for the unwrapped constant or variable where appropriate.
3.5.5 對可選屬性解包時，對解開的常量或變量使用相同的名稱。

guard let myValue = myValue else {
    return
}

3.5.6 Use XCTUnwrap instead of forced unwrapping in tests.
3.5.6 在單元測試中，對可選類型使用XCTUnwrap，而不用強制解包。

func isEvenNumber(_ number: Int) -> Bool {
    return number % 2 == 0
}

// PREFERRED
func testWithXCTUnwrap() throws {
    let number: Int? = functionThatReturnsOptionalNumber()
    XCTAssertTrue(isEvenNumber(try XCTUnwrap(number)))
}

// NOT PREFERRED
func testWithForcedUnwrap() {
    let number: Int? = functionThatReturnsOptionalNumber()
    XCTAssertTrue(isEvenNumber(number!)) // may crash the simulator
}

3.6 Protocols

3.6 協議

When implementing protocols, there are two ways of organizing your code:
實現協議時，有兩種方式來組織代碼：

Using // MARK: comments to separate your protocol implementation from the rest of your code
Using an extension outside your class/struct implementation code, but in the same source file
使用// MARK:注釋將您的協議實現與代碼的其余部分分開
在class/struct實現代碼之外使用擴展名，但在同一源代碼文件中

Keep in mind that when using an extension, however, the methods in the extension can't be overridden by a subclass, which can make testing difficult. If this is a common use case, it might be better to stick with method #1 for consistency. Otherwise, method #2 allows for cleaner separation of concerns.
請記住，在使用擴展時，擴展中的方法不能被子類覆蓋，否則可能會使測試變得困難。如果這種情況經常發生，為了保持一致性，最好堅持使用第一種方式。否則使用第二種方式，會使代碼分離得更干凈。

Even when using method #2, add // MARK: statements anyway for easier readability in Xcode's method/property/class/etc. list UI.
盡管使用第二種方式，也要添加// MARK:語句，以便在Xcode的method/property/class列表界面中更容易閱讀。

3.7 Properties

3.7 屬性

3.7.1 If making a read-only, computed property, provide the getter without the get {} around it.
3.7.1 如果要創建一個read-only計算屬性，請提供getter但無需使用get {}包住它。

var computedProperty: String {
    if someBool {
        return "I'm a mighty pirate!"
    }
    return "I'm selling these fine leather jackets."
}

3.7.2 When using get {}, set {}, willSet, and didSet, indent these blocks.
3.7.2 使用get {}，set {}，willSet 和 didSet 時，注意縮進代碼塊。
3.7.3 Though you can create a custom name for the new or old value for willSet/didSet and set, use the standard newValue/oldValue identifiers that are provided by default.
3.7.3 盡管您可以為 willSet/didSet 和 set 的新值或舊值創建自定義名稱，但推薦使用默認提供的標準名稱newValue/oldValue。

var storedProperty: String = "I'm selling these fine leather jackets." {
    willSet {
        print("will set to \(newValue)")
    }
    didSet {
        print("did set from \(oldValue) to \(storedProperty)")
    }
}

var computedProperty: String  {
    get {
        if someBool {
            return "I'm a mighty pirate!"
        }
        return storedProperty
    }
    set {
        storedProperty = newValue
    }
}

3.7.4 You can declare a singleton property as follows:
3.7.4 您可以用下面的方式聲明單例。

class PirateManager {
    static let shared = PirateManager()

    /* ... */
}

3.8 Closures

3.8 閉包

3.8.1 If the types of the parameters are obvious, it is OK to omit the type name, but being explicit is also OK. Sometimes readability is enhanced by adding clarifying detail and sometimes by taking repetitive parts away - use your best judgment and be consistent.
3.8.1 如果參數的類型明顯，可以省略類型名稱，當然顯式類型也可以。有時可以通過添加澄清細節來提高可讀性，有時通過刪除重復的部分來提高可讀性——使用你的最佳判斷力并保持一致性。

// omitting the type
doSomethingWithClosure() { response in
    print(response)
}

// explicit type
doSomethingWithClosure() { response: NSURLResponse in
    print(response)
}

// using shorthand in a map statement
[1, 2, 3].flatMap { String($0) }

譯者注：閉包中參數如果能清楚地推測出類型，可以不用寫類型，否則還是把類型寫出來提高可讀性。

3.8.2 If specifying a closure as a type, you don’t need to wrap it in parentheses unless it is required (e.g. if the type is optional or the closure is within another closure). Always wrap the arguments in the closure in a set of parentheses - use () to indicate no arguments and use Void to indicate that nothing is returned.
3.8.2 如果將閉包指定為類型，不需要將其包裝在括號中，除非有必要（例如，如果類型是可選的或閉包在另一個閉包中）。始終將閉包中的參數包裹在一組括號中 - 使用 () 表示沒有參數，使用 Void 表示不返回任何內容。

let completionBlock: (Bool) -> Void = { (success) in
    print("Success? \(success)")
}

let completionBlock: () -> Void = {
    print("Completed!")
}

let completionBlock: (() -> Void)? = nil

3.8.3 Keep parameter names on same line as the opening brace for closures when possible without too much horizontal overflow (i.e. ensure lines are less than 160 characters).
3.8.3 在沒有太多水平溢出的情況下，盡可能將參數名稱與閉包的左大括號保持在同一行（即確保行少于 160 個字符）。
3.8.4 Use trailing closure syntax unless the meaning of the closure is not obvious without the parameter name (an example of this could be if a method has parameters for success and failure closures).
3.8.4 使用尾隨閉包語法，除非閉包的含義在沒有參數名稱的情況下不明顯（例如，如果方法具有成功和失敗閉包的參數）。

// trailing closure
doSomething(1.0) { (parameter1) in
    print("Parameter 1 is \(parameter1)")
}

// no trailing closure
doSomething(1.0, success: { (parameter1) in
    print("Success with \(parameter1)")
}, failure: { (parameter1) in
    print("Failure with \(parameter1)")
})

譯者注：其實Xcode中回車補全閉包參數時自動轉化為尾隨閉包了，有必要的情況下可以自己手寫補全閉包。

3.9 Arrays

3.9 數組

3.9.1 In general, avoid accessing an array directly with subscripts. When possible, use accessors such as .first or .last, which are optional and won’t crash. Prefer using a for item in items syntax when possible as opposed to something like for i in 0 ..< items.count. If you need to access an array subscript directly, make sure to do proper bounds checking. You can use for (index, value) in items.enumerated() to get both the index and the value.
3.9.1 一般情況下，避免使用下標直接訪問數組。如果可能，請使用諸如.first或.last之類的訪問器，它們是可選的并且不會崩潰。盡可能使用for item in items語法，而不是像for i in 0 ..< items.count這樣的語法。如果您需要直接訪問數組下標，請確保進行適當的邊界檢查。您可以在 items.enumerated()中使用 for (index, value) 來獲取索引和值。
3.9.2 Never use the += or + operator to append/concatenate to arrays. Instead, use .append() or .append(contentsOf:) as these are far more performant (at least with respect to compilation) in Swift's current state. If you are declaring an array that is based on other arrays and want to keep it immutable, instead of let myNewArray = arr1 + arr2, use let myNewArray = [arr1, arr2].joined().
3.9.2 切勿使用 += 或 + 運算符來追加/連接到數組。相反，使用 .append() 或 .append(contentsOf:) 因為它們在 Swift 當前狀態下的性能要高得多（至少在編譯方面）。如果您要聲明一個基于其他數組的數組并希望使其保持不變，請使用let myNewArray = [arr1, arr2].joined()而不是let myNewArray = arr1 + arr2。

譯者注：這點我自己做的不好，jioned()真的很少用，相反數組+真的很好用，要舍棄真的有點舍不得，今后會多了解兩者的使用場景。

3.10 Error Handling

3.10 錯誤處理

Suppose a function myFunction is supposed to return a String, however, at some point it can run into an error. A common approach is to have this function return an optional String? where we return nil if something went wrong.
假設函數myFunction 應該返回一個String，但是，在某些時候它可能會遇到錯誤。常見的做法是讓這個函數返回一個可選的 String?，如果出現問題，我們就返回 nil。

Example:
例子：

func readFile(named filename: String) -> String? {
    guard let file = openFile(named: filename) else {
        return nil
    }

    let fileContents = file.read()
    file.close()
    return fileContents
}

func printSomeFile() {
    let filename = "somefile.txt"
    guard let fileContents = readFile(named: filename) else {
        print("Unable to open file \(filename).")
        return
    }
    print(fileContents)
}

Instead, we should be using Swift's try/catch behavior when it is appropriate to know the reason for the failure.
如果我們希望了解失敗原因，可以使用Swift 的 try/catch。

You can use a struct such as the following:
您可以使用struct，例如：

struct Error: Swift.Error {
    public let file: StaticString
    public let function: StaticString
    public let line: UInt
    public let message: String

    public init(message: String, file: StaticString = #file, function: StaticString = #function, line: UInt = #line) {
        self.file = file
        self.function = function
        self.line = line
        self.message = message
    }
}

Example usage:
用法示例：

func readFile(named filename: String) throws -> String {
    guard let file = openFile(named: filename) else {
        throw Error(message: "Unable to open file named \(filename).")
    }

    let fileContents = file.read()
    file.close()
    return fileContents
}

func printSomeFile() {
    do {
        let fileContents = try readFile(named: filename)
        print(fileContents)
    } catch {
        print(error)
    }
}

There are some exceptions in which it does make sense to use an optional as opposed to error handling. When the result should semantically potentially be nil as opposed to something going wrong while retrieving the result, it makes sense to return an optional instead of using error handling.
在某些例外情況下，使用可選項確實比錯誤處理更有意義。當結果在語義上 可能是 nil 而不是在檢索結果時出現錯誤時，返回一個可選項比使用錯誤處理更有意義。

In general, if a method can "fail", and the reason for the failure is not immediately obvious if using an optional return type, it probably makes sense for the method to throw an error.
一般來說，如果一個方法可能會失敗，并且如果使用可選返回類型，但失敗的原因不是很明顯，那么該方法拋出錯誤可能會更有意義。

3.11 Using `guard` Statements

3.11 使用`guard` 語句

3.11.1 In general, we prefer to use an "early return" strategy where applicable as opposed to nesting code in if statements. Using guard statements for this use-case is often helpful and can improve the readability of the code.
3.11.1 一般來說，我們更喜歡在適用的情況下使用“提前返回”策略，而不是在 if 語句中嵌套代碼。在這個用例中使用 guard 語句通常很有幫助，并且可以提高代碼的可讀性。

// PREFERRED
func eatDoughnut(at index: Int) {
    guard index >= 0 && index < doughnuts.count else {
        // return early because the index is out of bounds
        return
    }

    let doughnut = doughnuts[index]
    eat(doughnut)
}

// NOT PREFERRED
func eatDoughnut(at index: Int) {
    if index >= 0 && index < doughnuts.count {
        let doughnut = doughnuts[index]
        eat(doughnut)
    }
}

3.11.2 When unwrapping optionals, prefer guard statements as opposed to if statements to decrease the amount of nested indentation in your code.
3.11.2 展開可選項時，更喜歡使用 guard 語句而不是 if 語句，以減少代碼中嵌套縮進的數量。

// PREFERRED
guard let monkeyIsland = monkeyIsland else {
    return
}
bookVacation(on: monkeyIsland)
bragAboutVacation(at: monkeyIsland)

// NOT PREFERRED
if let monkeyIsland = monkeyIsland {
    bookVacation(on: monkeyIsland)
    bragAboutVacation(at: monkeyIsland)
}

// EVEN LESS PREFERRED
if monkeyIsland == nil {
    return
}
bookVacation(on: monkeyIsland!)
bragAboutVacation(at: monkeyIsland!)

3.11.3 When deciding between using an if statement or a guard statement when unwrapping optionals is not involved, the most important thing to keep in mind is the readability of the code. There are many possible cases here, such as depending on two different booleans, a complicated logical statement involving multiple comparisons, etc., so in general, use your best judgement to write code that is readable and consistent. If you are unsure whether guard or if is more readable or they seem equally readable, prefer using guard.
3.11.3 在不涉及展開可選項的情況下決定使用if語句還是guard語句時，要記住的最重要的事情是代碼的可讀性。這里有很多可能的情況，比如依賴于兩個不同的布爾值，一個復雜的邏輯語句涉及多重比較等等，所以一般來說，使用你最好的判斷來編寫可讀且一致的代碼。如果您不確定 guard 或 if 是否更具可讀性，或者它們看起來同樣可讀，請首選使用 guard。

// an `if` statement is readable here
if operationFailed {
    return
}

// a `guard` statement is readable here
guard isSuccessful else {
    return
}

// double negative logic like this can get hard to read - i.e. don't do this
guard !operationFailed else {
    return
}

3.11.4 If choosing between two different states, it makes more sense to use an if statement as opposed to a guard statement.
3.11.4 如果在兩個不同的狀態之間進行選擇，使用 if 語句比使用 guard 語句更有意義。

// PREFERRED
if isFriendly {
    print("Hello, nice to meet you!")
} else {
    print("You have the manners of a beggar.")
}

// NOT PREFERRED
guard isFriendly else {
    print("You have the manners of a beggar.")
    return
}

print("Hello, nice to meet you!")

3.11.5 You should also use guard only if a failure should result in exiting the current context. Below is an example in which it makes more sense to use two if statements instead of using two guards - we have two unrelated conditions that should not block one another.
3.11.5 僅當失敗導致退出當前上下文時，您才可以使用guard。下面是一個示例，這里使用兩個 if 語句而不應該使用兩個 guard 語句——這里是兩個不應該相互阻塞的不相關條件。

if let monkeyIsland = monkeyIsland {
    bookVacation(onIsland: monkeyIsland)
}

if let woodchuck = woodchuck, canChuckWood(woodchuck) {
    woodchuck.chuckWood()
}

3.11.6 Often, we can run into a situation in which we need to unwrap multiple optionals using guard statements. In general, combine unwraps into a single guard statement if handling the failure of each unwrap is identical (e.g. just a return, break, continue, throw, or some other @noescape).
3.11.6 通常，我們會遇到需要使用 guard 語句解開多個可選項的情況。通常，如果處理每個解包的失敗是相同的（例如，只是一個 return、break、continue、throw 或其他一些 @noescape），則將多個解包語句合并為一個 guard 語句。

// combined because we just return
guard let thingOne = thingOne,
    let thingTwo = thingTwo,
    let thingThree = thingThree else {
    return
}

// separate statements because we handle a specific error in each case
guard let thingOne = thingOne else {
    throw Error(message: "Unwrapping thingOne failed.")
}

guard let thingTwo = thingTwo else {
    throw Error(message: "Unwrapping thingTwo failed.")
}

guard let thingThree = thingThree else {
    throw Error(message: "Unwrapping thingThree failed.")
}

3.11.7 Don’t use one-liners for guard statements.
3.11.7 不要在 guard 語句中使用單行。

// PREFERRED
guard let thingOne = thingOne else {
    return
}

// NOT PREFERRED
guard let thingOne = thingOne else { return }

4. Documentation/Comments

4.1 Documentation

If a function is more complicated than a simple O(1) operation, you should generally consider adding a doc comment for the function since there could be some information that the method signature does not make immediately obvious. If there are any quirks to the way that something was implemented, whether technically interesting, tricky, not obvious, etc., this should be documented. Documentation should be added for complex classes/structs/enums/protocols and properties. All public functions/classes/properties/constants/structs/enums/protocols/etc. should be documented as well (provided, again, that their signature/name does not make their meaning/functionality immediately obvious).
如果函數比簡單的 O(1) 操作更復雜，您通常應該考慮為函數添加 doc 注釋，因為可能存在一些方法簽名（方法名和參數列表）并不是那么一目了然。如果某些方法的實現方式有任何不易理解的代碼，都應該記錄下來。應該為復雜的類/結構/枚舉/協議和屬性添加文檔。所有public函數/類/屬性/常量/結構/枚舉/協議/等。也應該記錄在案（同樣前提是它們的簽名/名稱不能使功能一目了然）。

After writing a doc comment, you should option click the function/property/class/etc. to make sure that everything is formatted correctly.
編寫文檔注釋后，您應該選擇單擊函數/屬性/類/等，以確保所有內容格式正確。

Be sure to check out the full set of features available in Swift's comment markup described in Apple's Documentation.
請務必查看 Swift 注釋標記中可用的全套功能Apple 文檔中的描述。

Guidelines:
準則：

4.1.1 160 character column limit (like the rest of the code).
4.1.1 160 個字符的列限制（與代碼的其余部分一樣）。
4.1.2 Even if the doc comment takes up one line, use block (/** */).
4.1.2 即使文檔注釋占一行，也要使用block (/** */)。
4.1.3 Do not prefix each additional line with a *.
4.1.3 不要在每個附加行前加上 *。
4.1.4 Use the new - parameter syntax as opposed to the old :param: syntax (make sure to use lower case parameter and not Parameter). Option-click on a method you wrote to make sure the quick help looks correct.
4.1.4 使用新的 - parameter 語法而不是舊的 :param: 語法（確保使用小寫的 parameter 而不是 Parameter）。按住 Option 鍵單擊您編寫的方法以確保快速幫助看起來正確。

class Human {
    /**
     This method feeds a certain food to a person.

     - parameter food: The food you want to be eaten.
     - parameter person: The person who should eat the food.
     - returns: True if the food was eaten by the person; false otherwise.
    */
    func feed(_ food: Food, to person: Human) -> Bool {
        // ...
    }
}

4.1.5 If you’re going to be documenting the parameters/returns/throws of a method, document all of them, even if some of the documentation ends up being somewhat repetitive (this is preferable to having the documentation look incomplete). Sometimes, if only a single parameter warrants documentation, it might be better to just mention it in the description instead.
4.1.5 如果您要記錄方法的參數/返回/拋出異常，請記錄所有這些，即使某些文檔最終有些啰嗦（這比不完整的文檔更好）。有時，如果只有一個參數需要記錄，最好在描述中提及它。
4.1.6 For complicated classes, describe the usage of the class with some potential examples as seems appropriate. Remember that markdown syntax is valid in Swift's comment docs. Newlines, lists, etc. are therefore appropriate.
4.1.6 對于復雜的類，用一些看起來合適的潛在例子來描述類的用法。請記住 Markdown 語法在 Swift 的注釋文檔中是有效的。因此，換行符、列表等是合適的。

/**
 ## Feature Support

 This class does some awesome things. It supports:

 - Feature 1
 - Feature 2
 - Feature 3

 ## Examples

 Here is an example use case indented by four spaces because that indicates a
 code block:

     let myAwesomeThing = MyAwesomeClass()
     myAwesomeThing.makeMoney()

 ## Warnings

 There are some things you should be careful of:

 1. Thing one
 2. Thing two
 3. Thing three
 */
class MyAwesomeClass {
    /* ... */
}

4.1.7 When mentioning code, use code ticks - `

/**
 This does something with a `UIViewController`, perchance.
 - warning: Make sure that `someValue` is `true` before running this function.
 */
func myFunction() {
    /* ... */
}

4.1.8 When writing doc comments, prefer brevity where possible.
4.1.8 在編寫文檔注釋時，盡可能簡潔。

4.2 Other Commenting Guidelines

4.2 其他注釋指南

4.2.1 Always leave a space after //.
4.2.1 始終在//后面加上一個空格.
4.2.2 Always leave comments on their own line.
4.2.2 注釋必須另起一行。
4.2.3 When using // MARK: - whatever, leave a newline after the comment.
4.2.3 使用// MARK: - whatever時，在注釋后換行。

class Pirate {

    // MARK: - instance properties

    private let pirateName: String

    // MARK: - initialization

    init() {
        /* ... */
    }

}

原文鏈接

Swift Style Guide

三个男躁一个女,国精产品一区一手机的秘密,麦子交换系列最经典十句话,欧美 国产 综合 欧美 视频

Swift 代碼規范中文-Swift Style Guide

Swift Style Guide

Swift代碼規范指南

Table Of Contents

目錄

1. Code Formatting

1. 代碼格式

2. Naming

2. 命名

3. Coding Style

3. 編碼風格

3.1 General

3.1 概述

3.2 Access Modifiers

3.2 訪問修飾符

3.3 Custom Operators

3.3 自定義操作符

3.4 Switch Statements and enums

3.4 Switch語句和enum

3.5 Optionals

3.5 可選

3.6 Protocols

3.6 協議

3.7 Properties

3.7 屬性

3.8 Closures

3.8 閉包

3.9 Arrays

3.9 數組

3.10 Error Handling

3.10 錯誤處理

3.11 Using guard Statements

3.11 使用guard 語句

4. Documentation/Comments

4.1 Documentation

4.2 Other Commenting Guidelines

4.2 其他注釋指南

原文鏈接

推薦閱讀更多精彩內容

三个男躁一个女,国精产品一区一手机的秘密,麦子交换系列最经典十句话,欧美国产综合欧美视频

3.4 Switch Statements and `enum`s

3.4 Switch語句和`enum`

3.11 Using `guard` Statements

3.11 使用`guard` 語句