-1 I've followed this discussion since the beginning, and I feel the usage is clear given that for...in is a *data-driven* loop
I wouldn't mind renaming to "if" if there is some confusion, but I think we use "where" consistently in the language (and Dave Abrahams proposal for closure argument names takes this further), so could be argued that it's already clear. Perhaps we should use "where" consistently for data-filtering operations, and possibly rename the generic constraint specifier. If we wanted to be really rigorously consistent. Karl Sent from my new Email (https://itunes.apple.com/app/apple-store/id922793622?pt=814382&mt=8&ct=my_new_email) > > On Jun 23, 2016 at 6:12 AM, <Chris Lattner via swift-evolution > (mailto:swift-evolution@swift.org)> wrote: > > > > Hello Swift community, > > The review of "SE-0105: Removing Where Clauses from For-In Loops" begins now > and runs through June 29. (x-apple-data-detectors://1) The proposal is > available here: > > > https://github.com/apple/swift-evolution/blob/master/proposals/0105-remove-where-from-forin-loops.md > > (https://github.com/apple/swift-evolution/blob/master/proposals/0105-remove-where-from-forin-loops.mdReviews) > > Reviews > (https://github.com/apple/swift-evolution/blob/master/proposals/0105-remove-where-from-forin-loops.mdReviews) > 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-evolutionor) > > or (https://lists.swift.org/mailman/listinfo/swift-evolutionor), 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 > (x-apple-data-detectors://4) under review through constructive criticism and > contribute to 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.mdThank) > > Thank (https://github.com/apple/swift-evolution/blob/master/process.mdThank) > you, > > -Chris Lattner > Review Manager > > > _______________________________________________ > swift-evolution mailing list (mailto:listswift-evolution@swift.orghttps) > swift-evolution@swift.org (mailto:listswift-evolution@swift.orghttps) > https > (mailto:listswift-evolution@swift.orghttps)://lists.swift.org/mailman/listinfo/swift-evolution >
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
