The title of this email seems a little off, it does not match the enclosed proposal, but responded to the proposal enclosed which is the Tuple comparison proposal.
> or, 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 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? It does seem like a good interim solution until a more general approach can be made that supports N-arity. > * Is the problem being addressed significant enough to warrant a change > to Swift? Yes. It is not great that these are not easily compared. > * Does this proposal fit well with the feel and direction of Swift? Yes. > * If you have you used other languages or libraries with a similar > feature, how do you feel that this proposal compares to those? Nothing that would influence this. > * How much effort did you put into your review? A glance, a quick > reading, or an in-depth study? I read the proposal. > > 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> > > Cheers, > Dave Abrahams > 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
