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

[T.J. Usiyan]

+1

On Fri, Mar 11, 2016 at 1:27 PM, Chris Wagner via swift-evolution <
swift-evolution at swift.org> wrote:

>
> *What is your evaluation of the proposal?*
>
>
> A huge +1.
>
>
> *Is the problem being addressed significant enough to warrant a change to
> Swift?*
>
>
> Absolutely, named parameters are immensely beneficial
>
>
> *Does this proposal fit well with the feel and direction of Swift?*
>
>
> 100%
>
>
> *If you have used other languages or libraries with a similar feature, how
> do you feel that this proposal compares to those?*
>
> NA
>
>
> *How much effort did you put into your review? A glance, a quick reading,
> or an in-depth study?*
>
> A fair deal, read the proposal. I’ve also been annoyed for awhile by the
> omission of the first param name in my development that I often explicitly
> add it.
>
>
> On Mar 11, 2016, at 11:01 AM, Chris Lattner <clattner at apple.com> wrote:
>
> 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-announce mailing list
> swift-evolution-announce at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution-announce
>
>
>
> _______________________________________________
> 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/678aa911/attachment.html>