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

[davesweeris at mac.com]

Not if you can’t figure out how to write the protocol such that it doesn’t refer to Self, have typealiases, or do something else that means you can only use it as a generic constraint rather than an actual type.

> On Jan 10, 2016, at 20:59, Douglas Gregor via swift-evolution <swift-evolution at swift.org> wrote:
> 
> I’m not nearly as convinced that it’s worth doing. It’s a small feature with a small win, and I tend to think that protocols are a better answer for most problems for which one would reflexively reach for an abstract class.