> As it is right now in Swift, accessing methods directly gives you a curried
> function back, which expects the object instance as argument in the first
> call, and the rest in the second call.
That was my first thought when I read the proposal - and as there is already a
change planned for currying, it could be easy to change the way it works for
methods.
I really don't think that ".method()" improves clarity, but "Type.method"
definitely does.
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
