[swift-evolution] [swift-evolution-announce] SE-0171: Reduce with inout

[Howard Lovatt]

>>> review of “SE-0171: Reduce with inout" 
>>> 
>>> 	• What is your evaluation of the proposal?

Good addition. Into is good name. 

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

Yes. I have written my own version. 

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

Yes. Improving collections worth while. 

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

The other liveries I have used with collect have had mutable versions. The Swift existing immutable version is the outlier for me. 

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

Quick read. 

-- Howard. 

> On 15 Apr 2017, at 4:41 am, Ben Cohen <ben_cohen at apple.com> wrote:
> 
> Apologies, if you are reading this in HTML the links appear to be pointing to the incorrect proposal. 
> 
> Here is the corrected link:
> 
> https://github.com/apple/swift-evolution/blob/master/proposals/0171-reduce-with-inout.md
> 
>> On Apr 14, 2017, at 11:37 AM, Ben Cohen <ben_cohen at apple.com> wrote:
>> 
>> Hello Swift community,
>> 
>> The review of “SE-0171: Reduce with inout" begins now and runs through the Friday after next, April 14th. The proposal is available here:
>> 	https://github.com/apple/swift-evolution/blob/master/proposals/0171-reduce-with-inout.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:
>> 
>> 	Proposal link: https://github.com/apple/swift-evolution/blob/master/proposals/0171-reduce-with-inout.md
>> 
>> 	Reply text
>> 
>> 	Other replies
>> 
>> 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,
>> 
>> Ben Cohen
>> Review Manager
>> 
>> 
>> _______________________________________________
>> swift-evolution-announce mailing list
>> swift-evolution-announce at swift.org
>> https://lists.swift.org/mailman/listinfo/swift-evolution-announce
> 
> _______________________________________________
> swift-evolution-announce mailing list
> swift-evolution-announce at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution-announce
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170415/7ca1cebf/attachment.html>