[swift-evolution] Proposal: Change of syntax for class protocols

Stephen Celis stephen.celis at gmail.com
Mon Dec 7 10:51:00 CST 2015


Do others find themselves implementing class-only protocols often? They
seem to be the exception, rather than the rule, to me.

Stephen

On Mon, Dec 7, 2015 at 11:32 AM, Sean Heber via swift-evolution <
swift-evolution at swift.org> wrote:

> I found this odd, too. I don’t know what kind of parsing ramifications
> this might have, but I like the idea. I suppose one downside is that it
> makes protocols for classes seem somehow special or different from other
> protocols - but then again, they kind of are!
>
> l8r
> Sean
>
>
> > On Dec 7, 2015, at 10:00 AM, Matthew Cheok via swift-evolution <
> swift-evolution at swift.org> wrote:
> >
> > Currently, we declare class protocols with the following syntax:
> >
> > protocol TestProtocol: class, OtherProtocol {}
> >
> > This is odd for a few reasons:
> > 1) The keyword class exists in the middle of the declaration
> > 2) The keyword class follows the colon and looks a lot like inheritance
> > 3) The keyword class occupies a somewhat arbitrary first position after
> the colon (otherwise we have an error)
> >
> > We also have another use of the class keyword as a modifier when
> declaring class methods:
> >
> > class func doSomething() {}
> >
> > I’m suggesting a change of syntax that rectifies the above issues:
> >
> > class protocol TestProtocol: OtherProtocol {}
> >
> > Would love to hear other thoughts on this.
> >
> > - Matthew
> >
> > _______________________________________________
> > swift-evolution mailing list
> > swift-evolution at swift.org
> > https://lists.swift.org/mailman/listinfo/swift-evolution
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20151207/9cbb4a03/attachment.html>


More information about the swift-evolution mailing list