See the text below the quoted paragraph in my email - I've mentioned how extending the protocol can be helpful e.g. in case of delegate protocols - where you may want to extend the protocol in subclasses of the delegated class introducing new methods for the delegate. In such scenarios, forcing them final is not an option.
21. 5. 2016 v 14:25, Brent Royal-Gordon <[email protected]>: >> Making them final is not a good idea. I see the default implementations in >> protocols as something that should replace the optional methods in @objc >> protocols. > > We aren't discussing default implementations. We're discussing methods that > are listed *only* in the protocol extension, not in the protocol itself. > These methods cannot be "overridden" in the way that a defaulted protocol > method can be; I think it's safest to outlaw any attempt to "override" them > at all. > > -- > Brent Royal-Gordon > Architechies > _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
