Open Radar

 
Summary:
When a multi-parameter function signature includes comments, it will incorrectly generate the header documentation boilerplate, overriding actual parameters with these comments

Steps to Reproduce:
Create the following function:

```swift
func hello(
    name: String, /* ABC: make this a concrete type */
    lastName: String /* DEF: make this a concrete type */
) -> String {
    return "Hello, \(name) \(lastName)!"
}
```

then hit ⌥+⌘+/ (Editor -> Structure -> Add Documentation

Expected Results:
It should create the following header:

```swift
/// <#Description#>
///
/// - Parameters:
///   - name: <#name description#>
///   - lastName: <#lastName description#>
/// - Returns: <#return value description#>
```

Actual Results:
It returns the following header:

```swift
/// <#Description#>
///
/// - Parameters:
///   - name: <#name description#>
///   - ABC: <#ABC description#>
/// - Returns: <#return value description#>
```

Version:
Xcode 10.1

Notes:
This only seems to happen with a multi-parameter function.

This, for example, works as expected:

```swift
func hello(
    name: String // FIXME: make this a concrete type
) -> String {
    return "Hello, \(name)!"
}
```

and generates

```swift
/// <#Description#>
///
/// - Parameter name: <#name description#>
/// - Returns: <#return value description#>
```

It should also be noted that in the breaking example, only the second parameter breaks, using the “ABC” as its “parameter name”. The second parameter is ignored.

It does not matter if you are using a double slash or a opening-and-closing comment style.