[swift-evolution] [Pitch] Setup Block

Jay Abbott jay at abbott.me.uk
Sun Nov 20 11:01:34 CST 2016

Hi Andrew,

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.

On Sun, 20 Nov 2016 at 09:58 Tino Heth via swift-evolution <
swift-evolution at swift.org> wrote:

> 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.
> 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.
> _______________________________________________
> 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/20161120/82307e42/attachment.html>

More information about the swift-evolution mailing list