Open Radar

 
Summary:
When passing `init` methods to higher order functions at the type level, you need to use `self.init` or else the compiler throws errors. However, the errors the compiler throws aren’t helpful and don’t tell you what the actual problem is.

Steps to Reproduce:
1. Create a simple struct:

```swift
struct Foo {
  let foo: String
}
```

2. Add a type level method to the struct, and pass the init method without prefixing with `self`:

```swift
extension Foo {
  static func bar(opt: String?) -> Foo? {
    return opt.map(init)
  }
}
```	

Expected Results:
Expect to see a helpful error message that describes the actual problem (that the init method must be invoked on an explicit type)

Actual Results:
Multiple error messages (up to 8, with some duplications) are thrown at the same time, none of which are helpful:

- Consecutive statements on a line must be separated by ‘;’
- Expected ‘,’ separator
- Expected ‘(‘ for initializer parameters
- Expected expression in list of expressions
- Expected ‘)’ in expression list
- Expected expression
- Initializers may only be declared within a type