> • What is your evaluation of the proposal? +1
> • Is the problem being addressed significant enough to warrant a change to > Swift? Yes, I’ve come across the issue a few times. > • Does this proposal fit well with the feel and direction of Swift? To me the solution seems a lot more intuitive than the proposed alternatives, so yes! > • 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? Read the proposal, and I’ve thought about the issue before when stumbling over this in my own code. > On 16 Mar 2016, at 18:55, Chris Lattner via swift-evolution > <[email protected]> wrote: > > Hello Swift community, > > The review of “Declare variables in 'case' labels with multiple patterns” > begins now and runs through March 21, 2016. The proposal is available here: > > > https://github.com/apple/swift-evolution/blob/master/proposals/0043-declare-variables-in-case-labels-with-multiple-patterns.md > > <https://github.com/apple/swift-evolution/blob/master/proposals/0043-declare-variables-in-case-labels-with-multiple-patterns.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: > > 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, > > -Chris > Review Manager > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
