<div dir="ltr"> • What is your evaluation of the proposal?<div><br></div><div>+1. I am happy to see this proposal.</div><div><br></div><div> • Is the problem being addressed significant enough to warrant a change to Swift?<br></div><div><br></div><div>Yes. In my experience, newcomers to Swift are often confused by parameter labels in general, and first parameters in particular, and they often get them wrong on their first few attempts.</div><div><br></div><div> • Does this proposal fit well with the feel and direction of Swift?<br></div><div><br></div><div>Yes, it fits well with Swift's API Design guidelines, especially "Clarity is more important than brevity" and "Clarity at the point of use".</div><div><br></div><div> • If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br></div><div><br></div><div>I have not used any languages that handle parameter labels quite like Swift does.</div><div><br></div><div> • How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br></div><div><br></div><div>Quick read. I'm ashamed to admit that I missed the other threads discussing this.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 11, 2016 at 10:52 PM, Paul Ossenbruggen via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""> • What is your evaluation of the proposal?<br>
<br>
</span> 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.<br>
<span class=""><br>
• Is the problem being addressed significant enough to warrant a change to Swift?<br>
</span>Yes<br>
<span class=""><br>
• Does this proposal fit well with the feel and direction of Swift?<br>
</span>Perhaps.<br>
<span class=""><br>
• If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br>
<br>
</span>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.<br>
<span class=""><br>
• How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br>
<br>
</span>Been following the thread and read proposal.<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</div></div></blockquote></div><br></div>