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

[Michael Buckley]

        • What is your evaluation of the proposal?

+1. I am happy to see this proposal.

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

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.

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

Yes, it fits well with Swift's API Design guidelines, especially "Clarity
is more important than brevity" and "Clarity at the point of use".

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

I have not used any languages that handle parameter labels quite like Swift
does.

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

Quick read. I'm ashamed to admit that I missed the other threads discussing
this.

On Fri, Mar 11, 2016 at 10:52 PM, Paul Ossenbruggen via swift-evolution <
swift-evolution at swift.org> wrote:

>         • 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?
> Yes
>
>         • Does this proposal fit well with the feel and direction of Swift?
> Perhaps.
>
>         • 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.
> _______________________________________________
> 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/20160311/c408bb2d/attachment.html>