<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div>On Sat, Jan 9, 2016, at 02:50 PM, Douglas Gregor wrote:<br></div>
<blockquote type="cite"><div><div>* What is your evaluation of the proposal?<br></div>
</div>
</blockquote><div> </div>
<div>+1<br></div>
<div> </div>
<blockquote type="cite"><div><div>* Is the problem being addressed significant enough to warrant a change to Swift?<br></div>
</div>
</blockquote><div> </div>
<div>Yes.<br></div>
<div> </div>
<blockquote type="cite"><div><div>* Does this proposal fit well with the feel and direction of Swift?<br></div>
</div>
</blockquote><div> </div>
<div>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.<br></div>
<div> </div>
<blockquote type="cite"><div><div><span style="white-space:pre;"></span>* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br></div>
</div>
</blockquote><div> </div>
<div>A quick reading.<br></div>
<div> </div>
<div>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.<br></div>
<div> </div>
<div>-Kevin Ballard<br></div>
</body>
</html>