As far as I know, you can only document the closure parameters if you label them:
/// Calls bar with "Hello, world"
/// - parameter bar: A closure to call
/// - parameter theString: A string to use
func foo(bar: (theString: String) -> Void) {
bar(theString: "Hello, world")
}
This is less than ideal: it forces you to use an argument label when you call the closure, and if there are naming conflicts, there seems no way to distinguish between the two.
Edit: As @Arnaud pointed out, you can use _
to prevent having to use the parameter label when calling the closure:
/// Calls bar with "Hello, world"
/// - parameter bar: A closure to call
/// - parameter theString: A string to use
func foo(bar: (_ theString: String) -> Void) {
bar("Hello, world")
}
In fact, this is the only valid approach in Swift 3 because parameter labels are no longer part of the type system (see SE-0111).
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…