<div dir="ltr"><div>Hi Andrew,<br><br></div>There is a similar discussion (in that it solves some aspects of the same problem) going on at the moment with the subject "Add code to super methods" - check it out. The parts of this problem it doesn't address is that you would still have to override multiple init methods to ensure your common setup was called regardless of which initialiser is used. However, your idea of a post-init call might solve some of of the other issues being discussed there and affect that discussion quite a bit. In other words, I think these two ideas might benefit from being considered together rather than as separate issues.<br></div><br><div class="gmail_quote"><div dir="ltr">On Sun, 20 Nov 2016 at 09:58 Tino Heth via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Initialization is already quite complex in Swift, so I'm very wary of adding new features and prefer Derricks idea over a new language feature.<br class="gmail_msg">
I hope Swift is still flexible enough for deep changes in this area — I guess enforcing that there is always a single designated initializer would not only improve on you usecase.<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
swift-evolution mailing list<br class="gmail_msg">
<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="gmail_msg">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="gmail_msg">
</blockquote></div>