<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">I think my point is that the 2.2 branch currently contains a broken implementation, so we have to do <i class="">something</i> there. We <i class="">don't</i> have to do anything in Swift 3.0, though, because the feature has been removed.</div><div class=""><br class=""></div><div class="">Jordan</div><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 15, 2016, at 10:20, David Farler <<a href="mailto:dfarler@apple.com" class="">dfarler@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Since the dynamic dispatch for super methods was already implemented and 2.2 was the active release on master, it seemed natural to propose it for that release at the time. Now that we've already branched for Swift-2.2, I wouldn't be vehemently opposed to not cherry-picking to 2.2.<br class=""><br class="">David<br class=""><br class=""><blockquote type="cite" class="">On Jan 11, 2016, at 1:53 PM, Jordan Rose <<a href="mailto:jordan_rose@apple.com" class="">jordan_rose@apple.com</a>> wrote:<br class=""><br class="">-1 from me. We should just go back to the old dispatch mechanism in Swift 2.2, since we're not using the dynamism for anything, and then in Swift 3.0 it's a non-issue, since there are no more curried function declarations and we can handle the other case.<br class=""><br class="">(This is not a very formal review, but my motivation is entirely implementation-based. I did talk to David internally before sending this.)<br class=""><br class="">Jordan<br class=""></blockquote><br class=""></div></div></blockquote></div><br class=""></body></html>