[swift-evolution] [Review] SE-0013 Remove Partial Application of Non-Final Super Methods
jordan_rose at apple.com
Fri Jan 15 12:46:52 CST 2016
I think my point is that the 2.2 branch currently contains a broken implementation, so we have to do something there. We don't have to do anything in Swift 3.0, though, because the feature has been removed.
> On Jan 15, 2016, at 10:20, David Farler <dfarler at apple.com> wrote:
> 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.
>> On Jan 11, 2016, at 1:53 PM, Jordan Rose <jordan_rose at apple.com> wrote:
>> -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.
>> (This is not a very formal review, but my motivation is entirely implementation-based. I did talk to David internally before sending this.)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution