[swift-evolution] [Review] SE-0053 Remove explicit use of let from Function Parameters

[Arthur Ariel Sabintsev]

+1. This seems like a nice and obvious change after the var proposal.
On Fri, Mar 25, 2016 at 12:14 PM Juan Ignacio Laube via swift-evolution <
swift-evolution at swift.org> wrote:

> * What is your evaluation of the proposal?
> +1. Since `let` is the default behaviour, and `var` usage has been
> deprecated, doesn’t make sense to have a keyword for this.
>
> * 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?
> Yes.
>
> * If you have you 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?
> Quick reading of the proposal.
>
>
> > On Mar 24, 2016, at 3:00 PM, Chris Lattner via swift-evolution <
> swift-evolution at swift.org> wrote:
> >
> > Hello Swift community,
> >
> > The review of "Remove explicit use of let from Function Parameters"
> begins now and runs through March 27th. The proposal is available here:
> >
> >
> https://github.com/apple/swift-evolution/blob/master/proposals/0053-remove-let-from-function-parameters.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.
> >
> >
> > 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 you 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 Lattner
> > Review Manager
> >
> >
> > _______________________________________________
> > swift-evolution mailing list
> > swift-evolution at swift.org
> > https://lists.swift.org/mailman/listinfo/swift-evolution
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
-- 
Best,

Arthur / Sabintsev.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160325/5a3887e2/attachment.html>