[swift-evolution] [Accepted] SE-0111: Remove type system significance of function argument labels

Cao Jiannan frogcjn at 163.com
Wed Jul 6 23:21:25 CDT 2016

func needsCallback(callback: (a: Int, b: Int) -> Void) {
    callback(a: 1,b: 2)

func needsCallback(callback: (Int, Int) -> Void) {
    callback(1, 2)

Is the first one will be forbidden?
So you'd like to keep the second one?

> 在 2016年7月7日,11:06,Chris Lattner via swift-evolution <swift-evolution at swift.org> 写道:
> Proposal Link: https://github.com/apple/swift-evolution/blob/master/proposals/0111-remove-arg-label-type-significance.md
> The review of "SE-0111: Remove type system significance of function argument labels " ran from June 30 ... July 4, 2016. The proposal has been *accepted*:
> The community and core team agree that this proposal will lead to a simplification and clarification of the type system, as well as a more clear user model for parameter labels.  In response to community feedback, the core team is accepting the proposal with a revision to allow “purely cosmetic” parameter labels in closure types for documentation (as outlined in the alternatives section).  The core team also wants to clarify that a call to a value of closure type would not allow use of any parameter labels, some interpretations thought that “arbitrary” parameter labels could be used.
> Thank you to Austin Zheng for driving this discussion forward!  I filed SR-2009 to track implementation work on this.
> -Chris Lattner
> Review Manager
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160707/2a56ff95/attachment.html>

More information about the swift-evolution mailing list