[swift-evolution] [Review] SE-0046 Establish consistent label behavior across all parameters including first labels

Kyle Sherman kyledsherman at gmail.com
Sun Mar 13 18:58:26 CDT 2016


What is your evaluation of the proposal?

Strong +1 from me. The first negative though I had when starting Swift the first day it came out was about the inconsistency of function/method/initializer argument names.

Is the problem being addressed significant enough to warrant a change to Swift?

Absolutely.

Does this proposal fit well with the feel and direction of Swift?

Definitely.

If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?

N/A

How much effort did you put into your review? A glance, a quick reading, or an in-depth study?

I read through the entire thing and have wanted this exact change from the first day I looked at the language. I highly support it.


> > What is your evaluation of the proposal?
> Strong +1
> 
> > Is the problem being addressed significant enough to warrant a change to Swift?
> Yes.
> 
> > Does this proposal fit well with the feel and direction of Swift?
> Fits very well. Anonymous first parameters are a relict of Objective-C and do not conform to new API Naming Guidelines.
> 
> > How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
> Quick read of the proposal document.
> 
> 
> Pozdrawiam – Regards,
> Adrian Kashivskyy
> 
> 
> > Wiadomość napisana przez Chris Lattner via swift-evolution<swift-evolution at swift.org(mailto:swift-evolution at swift.org)>w dniu 11.03.2016, o godz. 19:01:
> > Hello Swift community,
> > 
> > The review of “Establish consistent label behavior across all parameters including first labels” begins now and runs through March 15, 2016. The proposal is available here:
> > 
> > https://github.com/apple/swift-evolution/blob/master/proposals/0046-first-label.md
> > 
> > Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at:
> > https://lists.swift.org/mailman/listinfo/swift-evolution
> > 
> > or, if you would like to keep your feedback private, directly to the review manager. When replying, please try to keep the proposal link at the top of the message:
> > 
> > What goes into a review?
> > 
> > The goal of the review process is to improve the proposal under review through constructive criticism and, eventually, determine the direction of Swift. When writing your review, here are some questions you might want to answer in your review:
> > 
> > • What is your evaluation of the proposal?
> > • Is the problem being addressed significant enough to warrant a change to Swift?
> > • Does this proposal fit well with the feel and direction of Swift?
> > • If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
> > • How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
> > 
> > More information about the Swift evolution process is available at:
> > 
> > https://github.com/apple/swift-evolution/blob/master/process.md
> > 
> > Thank you,
> > 
> > -Chris
> > 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/20160313/86d3826d/attachment.html>


More information about the swift-evolution mailing list