* What is your evaluation of the proposal?
+1
* Is the problem being addressed significant enough to warrant a
change to Swift?
Yes.
* Does this proposal fit well with the feel and direction of Swift?
It doesn't really fit with Swift 2.x since it explicitly disallows
currying of a particular type of function call, but it does fit with
Swift 3.0, and that's kind of the whole point.
* How much effort did you put into your review? A glance, a quick
reading, or an in-depth study?
A quick reading.
Partial application of calls to super seems like an extremely niche use-
case, and one that can be trivially worked around by writing a local
closure, so it seems like a good tradeoff.
-Kevin Ballard
···
On Sat, Jan 9, 2016, at 02:50 PM, Douglas Gregor wrote: