• What is your evaluation of the proposal? +1 • Is the problem being addressed significant enough to warrant a change to Swift? Yes. I have often been frustrated by needing to break up conditions to make complex checks. I am not completely sure that this proposal addresses that issue but it is certainly a step in the direction of resolving it. • Does this proposal fit well with the feel and direction of Swift? Yes • If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those? Yes. I think that this compares well. It also helps stabilize coding style decisions. • How much effort did you put into your review? A glance, a quick reading, or an in-depth study? A couple quick readings.
On Fri, May 27, 2016 at 1:11 PM, Joe Groff <jgr...@apple.com> wrote: > Hello Swift community, > > The review of SE-0099 “Restructuring Condition Clauses” begins now and > runs through June 3, 2016. The proposal is available here: > > > https://github.com/apple/swift-evolution/blob/master/proposals/0099-conditionclauses.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/0099-conditionclauses.md > <https://github.com/apple/swift-evolution/blob/master/proposals/0099-conditionclauses.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, > > -Joe > > Review Manager > > _______________________________________________ > swift-evolution-announce mailing list > swift-evolution-annou...@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution-announce > >
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution