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

Paul Ossenbruggen possen at gmail.com
Sat Mar 12 00:52:06 CST 2016

	• What is your evaluation of the proposal?

 it makes  more sense and is more consistent and constructers require a first param it is a bit surprising that regular methods are different. Plus you can still omit the label on first param if it makes sense.  However, leaving out the param with this proposal is visually less appealing so people may be more tempted to add parameter labels than have underscores. 

	• 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?

Most other languages don’t do this so it is a bit of a surprise that Swift does, but it is perhaps a distinguishing characteristic and the current way makes people think a bit more perhaps about what their direct object is. 

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

Been following the thread and read proposal. 

More information about the swift-evolution mailing list