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

> On Apr 14, 2017, at 2:37 PM, Ben Cohen 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:

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

>>> 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

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

Yes, please. This will fill a major hole; namely, allowing us to populate collections functionally when the problem is too complex for a simple ‘map’ operation, or when the collection being built is something other than an array. Charles > On Apr 14, 2017, at 1:41 PM, Ben Cohen via

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

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 wrote: >