[swift-evolution] [Pitch] Requiring proactive overrides for default protocol implementations.

Erica Sadun erica at ericasadun.com
Sat Apr 30 20:00:41 CDT 2016

> On Apr 30, 2016, at 10:19 AM, T.J. Usiyan via swift-evolution <swift-evolution at swift.org> wrote:
> I agree that a keyword indicating intent would be nice, but I can't get behind override if what you're doing is providing your own implementation. I understand that we are trying to avoid adding keywords but could `implement` or a synonym work? If you override something that your superclass implements then you wouldn't need the `implement` keyword, just `override`. This has the benefit of making it clear that the method came from a protocol and not a superclass. 
> TJ

The discussion is pretty dead right now, but the key point is that override would only be used when replacing another required implementation member, not when just conforming by implementing a required member.

-- E

More information about the swift-evolution mailing list