is duplicated by:

• SR-1306 Inconsistent behavior with labeled type parameters

Issue Description:

I'm wondering what the reasoning is for allowing Types to be passed into a function without explicitly declaring .self if there is only one function parameter.

When ommitting .self:

• The function has 1 parameter: compiles

• The function has > 1 parameter: Expected member name or constructor call after type name

Take the following code:

func test<T: Any>(type: T.Type, two: String) {
    print(type)
}

func test<T: Any>(type: T.Type) {
    print(type)
}

test(Int.self) //no error
test(Int) //no error

test(Int.self, two: "") //no error
test(Int, two: "") //error: Expected member name or constructor call after type name

To give some background, I am trying to create a function with the signature

func get<T: Any>(path: String, _ star: T.Type, handler: (Request, T) throws -> Response)

That can be used like so

app.get("users", Int) { request, id in 
   print("You requested user with ID \(id)")
   ...
}

This get function works if you include .self after all of the Types, but that is not as clean and seems unnecessary unless I'm missing something.