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

David Sweeris davesweeris at mac.com
Tue Jul 25 23:39:52 CDT 2017

I think it's some subtlety... I might vaguely remember someone saying something about it. Since a proposal didn't come of that, I'm assuming there was a technical issue or something. I could easily be wrong, though.

- Dave Sweeris

> On Jul 25, 2017, at 9:36 PM, 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170725/0c316de6/attachment.html>

More information about the swift-evolution mailing list