Design syntax for function parameters and lambdas

[CohenArthur]

// switch from
func map[T, U](value: Maybe[T], f: func(T) -> U) -> Maybe[U] {}

// to
func map[T, U](value: Maybe[T], f: T -> U) -> Maybe[U] {}

[Skallwar]

What this will looks like when f take more than 1 arg?

func map[T, U, V](value: Maybe[T], f: T, V -> U) -> Maybe[U] {}

[CohenArthur]

What this will looks like when f take more than 1 arg?

func map[T, U, V](value: Maybe[T], f: T, V -> U) -> Maybe[U] {}

I was thinking something like

func map[T, U, V](value: Maybe[T], f: (T, V) -> U) -> Maybe[U] {}

which would also be the same syntax as having one tuple argument to the function, so I don't know if it's good or bad. Swift has had issues with this feature, but it's also a way more complex language, so maybe we can adopt it and not suffer: https://stackoverflow.com/questions/31320714/tuple-and-function-argument-in-swift

[Skallwar]

What the issue with the current syntax?

[CohenArthur]

it just looks less nice to me, I'd rather type int -> string than func(int) -> string