[swift-evolution] [Proposal draff] abstract classes and methods

Chris Lattner clattner at apple.com
Sat Jan 9 13:02:41 CST 2016

> On Jan 7, 2016, at 9:55 AM, David Scrève via swift-evolution <swift-evolution at swift.org> wrote:
> # Abstract classes and methods
> * Author(s): David Scrève
> ## Introduction
> When developing framework and reusable, we need to develop classes that are partially 
> abstract with partial implementation. Protocol and protocol extensions provide this, but 
> they cannot have attributes as classes have.
> A partial class combines the behavior of a class with the requirement of implementing methods
> in inherited class like protocols.

I tend to agree that adding abstract methods (and classes) is the right thing to do.  OOP is an important part of Swift, and is a great way for modeling certain classes of problems.

I wonder if we could simplify our initializer model if we had this, for example, could “required" initializers go away?


More information about the swift-evolution mailing list