> * What is your evaluation of the proposal? +1. After seeing an example of the current partition method (which I hadn't heard of before that) on the mailing list I tried to use it in our code, but it was too specialized for it to be a good fit. The new proposed method is more flexible and becomes a good building block for other code.
> * Is the problem being addressed significant enough to warrant a change to > Swift? Yes. It's fairly small, but not insignificant. > * 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? N/A > * How much effort did you put into your review? A glance, a quick reading, > or an in-depth study? Read the proposal (and tried to make use of the existing partition method once after having heard about it). _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
