[swift-evolution] Why couldn't a class call any of its superclass' initializers?

Benjamin Spratling bspratling at mac.com
Tue Jul 25 23:39:00 CDT 2017

It prevents accidental infinite loops of inits, which is possible in Obj-C.

> On Jul 26, 2017, at 12:36 AM, Daryle Walker via swift-evolution <swift-evolution at swift.org> wrote:
> [Sorry if this's been discussed before.]
> As long as the superclass sub-object gets initialized, it shouldn't matter if the initializer was designated or convenience. Is there some subtle step on the two-phase initialization I'm missing? Or is this a point to extend in a future version of Swift?
> Sent from my iPhone
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

More information about the swift-evolution mailing list