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 swift-evolution > <swift-evolution@swift.org> 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 > > <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_co...@apple.com >> <mailto:ben_co...@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 >> >> <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 >> <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 >> >> <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 >> <https://github.com/apple/swift-evolution/blob/master/process.md> >> >> Thank you, >> >> Ben Cohen >> Review Manager >> >> >> _______________________________________________ >> swift-evolution-announce mailing list >> swift-evolution-annou...@swift.org >> <mailto:swift-evolution-annou...@swift.org> >> https://lists.swift.org/mailman/listinfo/swift-evolution-announce >> <https://lists.swift.org/mailman/listinfo/swift-evolution-announce> > > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org <mailto:swift-evolution@swift.org> > https://lists.swift.org/mailman/listinfo/swift-evolution > <https://lists.swift.org/mailman/listinfo/swift-evolution>
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
